On 02/01/2018 11:08 AM, Simon Legner via aur-general wrote:
> Hi aur-general,
>
> as a maintainer of fifty-something AUR packages I found it difficult
> to keep track of new upstream versions. I would subscribe to various
> RSS feeds to keep track of some.
>
> Recently, I sat down and wrote a tool "aur-out-of-date" which, given a
> username or a list of packages, checks upstream for newer versions. It
> does so by inspecting the upstream URL and/or source URL, and calling
> a suitable API (github.com, registry.npmjs.org, pypi.python.org,
> cpan.org for now) to determine the latest released version.
> Out-of-date packages are output in red color on the command line.
>
> Give it a try:
> https://github.com/simon04/aur-out-of-date
> https://aur.archlinux.org/packages/aur-out-of-date/
>
> I'm happy to hear you feedback :)
> Simon
Awesome project. I made myself a similar one, a bash script that
checks GitHub API for new versions and updates the PKGBUILD. I was
planning on making something bigger with ruby, so it would be easily
extensible for non-regular cases (custom download pages etc.).
So I'm testing it at the moment. Looks cool.
First of all please modify the name of the
source in AUR. Some people use common source directories and that causes
conflicts. Secondly I think the program is too verbose. It would be
better readable displaying only brief information like:
"[OUT-OF-DATE] [$pkgname] Flagged: 1.0.0 -> 1.0.1"
or something like that. An option to ignore [UNKNOWN] packages would be
great too. I might be wrong, but it seems to go crazy with metapackages.
I don't know Go, but I'll try to patch if anything else comes to my mind.
Eli Schwartz via aur-general writes:
> 1) How does this handle PKGBUILDs that, say, have their homepage on
> github, but do not tag releases there -- because :( :( :( -- and instead
> push releases to PyPI or npmjs or something?
Imho such cases should be always reported upstream as that is a very bad
practice.
Marcin Wieczorek
signature.asc
Description: PGP signature
