[Slackbuilds-users] Repology: a way to track potential updates

[Jeremy Hansen]

On Mon, Jul 2, 2018, 4:20 AM Matteo Bernardini <matteo.bernardini at gmail.com>
wrote:

> 2018-07-02 12:08 GMT+02:00 Didier Spaier <didier at slint.fr>:
> > <rant>
> > Should we say "Thank you!" to a SlackBuild maintainer who provides an
> > upgrade to a shared library so that the 172 packages that rely on it are
> > now broken?
> > </rant>
> >
> > Yes repology is an useful tool, but blindly upgrade all and every
> > SlackBuild wouldn't be a good thing IMO.
> >
> > Have a good day,
> >
> > Didier
> >
> > PS Yes I know, the user has no obligation to apply an update. But not
> > all users are aware of the possible consequences of doing that.
>
> I totally agree.
>
> let me say also that the ones who browse repology and then write to
> maintainers "your SlackBuilds are outdated!" should take in account
> the above: there could be a lot of different reasons why some packages
> are not upgraded, not counting the false positives that repology often
> list as "upgrades".
>
> Matteo
>

I found I was losing track of what packages I was intending to keep at
their current versions and for what reason, so I ended up creating a page
on my github to allow me (and others) to easily see if I just wasn't aware
of an update or if I specifically decided to not update that program and
for what reason.

https://github.com/bassmadrigal/slackbuilds/blob/master/version-check.md

That being said, I do use repology all the time so I can be made aware of
some updates, then I can look over those updates and see if there's a good
enough reason to update them. It's a great additional tool in the toolbox.

Jeremy

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180702/a95b4f4c/attachment.html>