[Slackbuilds-users] Source code missing for some Slackbuilds scripts

[Arnaud]

Le 12 mars 2025 13:23:53 UTC, Jim <zsd+slackbuilds at jdvb.ca> a écrit :
>On Wed, Mar 12, 2025 at 18:18 (+1100), Duncan Roe wrote:
>
>> On Tue, Mar 11, 2025 at 02:46:23AM -0400, B. Watson wrote:
>
>>> Something I forgot to mention in my previous email...
>
>>> The reason I'm going into such detail about this is that I'm almost
>>> certainly the one who would have to do the work, if there's going to
>>> be a system that notifies maintainers about broken source URLs and
>>> outdated versions.
>
>> I agree it would be poor use of your time. Anyone who cares can browse
>> https://repology.org/repository/slackbuilds/problems for their email. That's
>> what I do.
>
>I think you missed or forgot about the discussion of "interrupts
>vs. polling" in your computer architecture and/or OS classes.  :-)
>
>I would much rather get interrupted by an email telling me I should/could
>update a package than spend my time polling one or more web sites to see if
>there is some issue.
>
>YMMV.
>
>                                Jim
>_______________________________________________
>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/
>

You can subscribe to your own maintainer RSS feed on repology, getting RSS notifications when one of your script is out-of-date, or becomes up-to-date after an SBo release.

This is quite efficient.

I use that and the RSS feeds from github or Pypi, for almost all my SlackBuilds.
But that's only because I've done this for a long time, it'd take too much efforts to do it from scratch now.

 - Yth.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250312/49914895/attachment.htm>