You are not logged in.

#1 2016-06-19 23:34:18

hhh
Meep!
Registered: 2015-09-17
Posts: 9,280
Website

[CLOSED] Neofetch upgrade, minor commits

@twoion, this is a BL package built from GitHub, right?

https://github.com/dylanaraps/neofetch#bunsenlabs

I'm sorry, n00b asks... these are just minor commits? Wondering if this is routine (most likely or you would have made an announcement) or if there is something to pay attention to here.

https://github.com/dylanaraps/neofetch/commits/master

Offline

#2 2016-06-20 01:10:21

twoion
ほやほや
Registered: 2015-08-10
Posts: 2,675

Re: [CLOSED] Neofetch upgrade, minor commits

What's the problem? Just upgrade; it's a git snapshot. I don't care how groundbraking any commits are when making these. Though there have been several improvements to neofetch. Just check out it's commit history.


Wahllos schlägt das Schicksal zu / heute ich und morgen du.

Offline

#3 2016-06-20 01:41:17

hhh
Meep!
Registered: 2015-09-17
Posts: 9,280
Website

Re: [CLOSED] Neofetch upgrade, minor commits

No problem, just curious. Minor commits, got it, thanks.

Offline

#4 2016-06-20 06:45:52

Head_on_a_Stick
Member
From: London
Registered: 2015-09-29
Posts: 8,759
Website

Re: [CLOSED] Neofetch upgrade, minor commits

Is there a reason we are using the latest HEAD rather than https://github.com/dylanaraps/neofetch/releases/tag/1.7?

I would think that using an actual release would be more consistent with the rest of the distribution.

Last edited by Head_on_a_Stick (2016-06-20 06:48:20)


“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII., 18.

Forum Rules   •   How to report a problem   •   Software that rocks

Offline

#5 2016-06-20 07:15:21

earlybird
ほやほや
Registered: 2015-12-16
Posts: 738
Website

Re: [CLOSED] Neofetch upgrade, minor commits

Head_on_a_Stick wrote:

Is there a reason we are using the latest HEAD rather than https://github.com/dylanaraps/neofetch/releases/tag/1.7?

I would think that using an actual release would be more consistent with the rest of the distribution.

I only build these things every other week so when I bother looking so I build it when I look at it. It doesn't matter if it's not a proper release for a toy program such as neofetch; besides I check if things are roughly working as expected before uploading the package. Getting the >200 commits to master since the last release with a lot of fixes going just by the commit messages doesn't hurt anybody either.

Using git HEAD instead of the latest release is an ad-hoc choice made by me. BL jessie-backports contains stuff from unstable anyway so I'm not breaking consistency either. Same for screenfetch.

Offline

#6 2016-06-23 20:03:44

KrunchTime
Member
Registered: 2015-09-29
Posts: 857

Re: [CLOSED] Neofetch upgrade, minor commits

Shouldn't this have been posted under the Development & Suggestions forum?

Offline

#7 2016-06-27 08:26:40

johnraff
nullglob
From: Nagoya, Japan
Registered: 2015-09-09
Posts: 6,538
Website

Re: [CLOSED] Neofetch upgrade, minor commits

Moved. It's closed anyway.


...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), idle Twitterings and GitStuff )

Introduction to the Bunsenlabs Lithium Desktop

Offline

Board footer

Powered by FluxBB