You are not logged in.

#1 2014-10-19 21:18:06

karol
Archivist
Registered: 2009-05-06
Posts: 25,440

Is it OK to flag out-of-date a -git package from the repos?

https://projects.archlinux.org/svntogit … ges/ps_mem seems to be based on a "release" mentioned in https://raw.githubusercontent.com/pixel … /ps_mem.py

# V3.3      24 Jun 2014
#   http://github.com/pixelb/scripts/commits/master/scripts/ps_mem.py

but the development moved https://github.com/pixelb/scripts/blob/ … /ps_mem.py -> https://github.com/pixelb/ps_mem/commits/master and there have been some commits recently.

What is the correct thing to do? It's a tiny package so updating it once in a while shouldn't be much of a burden, but then again, maybe it's better to upload a genuine -git package - ps_mem-git - to the AUR and use the latest and greatest code (I think it's called 'head', 'tip' or something) and not some fixed commit?

Offline

#2 2014-10-19 21:38:09

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,449
Website

Re: Is it OK to flag out-of-date a -git package from the repos?

I don't think it qualifies as out of date until the upstream source tags or labels one of those commits as the next version (3.4?), 3.3 is the current upstream release, and that's what's in the repos.

Until then, an aur -git package would make sense.  This is unless upstream has announced they will no longer make versioned releases.


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

Board footer

Powered by FluxBB