[Slackbuilds-users] Package versions

Ryan P.C. McQuen ryanpcmcquen at member.fsf.org
Thu Jan 19 19:54:59 UTC 2017

On 1/19/17, Eric Pratt <eric.b.pratt at gmail.com> wrote:
> I know I'm definitely guilty of letting my slackbuilds slip for long
> periods of time.  I'm trying to prevent that moving forward, but it's
> really mostly a matter of getting the time to do it and remembering to do
> it.  So I like the auto-updating idea.  It would get many of us past the
> remembering to do it part of the problem.
> But it would be difficult to do.  If there were a single standard database
> or even standard API on project homepages that could deliver the latest
> version numbers, then this would start to look good.  But everyone has
> their own method for announcing releases with their own formats.  We'd have
> to parse that out of each project page.  And people change their web page
> layouts and formats frequently enough for this to be an ongoing headache.
> If we're not updating our packages fast enough then we're not going to put
> even more effort into maintaining an auto-update feature.
> However, I do like the idea.  I try to automate everything I do at some
> point so this is an intriguing project.  Using ffmpeg as an example since
> it was already mentioned in this thread, an example to search for the
> current version number could be:
>   > wget -qO - "${PROJECT_URL}" | grep -o
> "${PROJECT_NAME}-[0-9][0-9A-Za-z.]*\.tar\.xz" | sort -n | tail -1
>   ffmpeg-3.2.2.tar.xz
>   >

I maintain a small set of builds for packages that I like to keep
up-to-date that do things like this:



More information about the SlackBuilds-users mailing list