[Slackbuilds-users] Repology: a way to track potential updates
dickson.tim at googlemail.com
Mon Jul 2 12:21:52 UTC 2018
... and this list well knows that some packages can't be "the latest"
because of breakage with stock slackware packages, or other
compatibility or stability reasons with other packages.
Regarding the issue Didier raised, i'm sure he has raised it with the
build provider, and this list ? It is always a good thing to raise for
testing when a library which is used by lots of other builds is due an
update, to avoid those sort of issues. I seem to remember ffmpeg update
was done this way. Repeating Petar, the intention was not to provoke.
after all, we're used to projects who upgrade library dependencies which
are more recent than what is available on sbo or slackware, leaving us
to try and patch them, just to get the software working, because
upstream don't want to keep older compatibility.
These issues appear both ways.
I still like having all builds presented together as repology.org does,
even if sometimes you have to say software X is "older" because of Y;
and if there is an issue with version detection, they are generally good
at updating it if you let them know.
On 02/07/2018 12:19, Petar Petrov wrote:
> 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>:
>>> 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?
>>> Yes repology is an useful tool, but blindly upgrade all and every
>>> SlackBuild wouldn't be a good thing IMO.
>>> Have a good day,
>>> 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".
>> SlackBuilds-users mailing list
>> SlackBuilds-users at slackbuilds.org
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
More information about the SlackBuilds-users