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

Petar Petrov slackalaxy at gmail.com
Mon Jul 2 11:19:55 UTC 2018

Hi all,

it was not my intention to provoke rants of any sort... also, i see
now, that I should have read the SBo mailing list more carefully
before posting about stuff you already know. Simply, *for me* Repology
turned out to be useful, and decided to bring it up. For example,
repology pointed out that Perlprimer and primer3 (as well as some
more) have new versions, which not announced on their webpages.


On 2 July 2018 at 13:20, 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
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/

More information about the SlackBuilds-users mailing list