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

[Tim Dickson]

agreed.
I have my own script that checks the packages I maintain for updates, 
(and also some other ones I keep a repo of)
That highlights when there is an update, or a change in the website 
broke my scraping script.

We also have https://sourceforge.net/projects/slackbuildsdirectlinks/ 
which we can use for those projects which
keep changing, or  removing source code/links so you don't loose access 
to source for existing scripts where projects don't keep older versions.

It would be more useful to have a location containing a list of the 
latest packages which can be checked programmatically
by those who want to automate their own checking. To a certain extent 
repology.org can do this, but the problems of distro's rolling git 
pushes as releases makes it less useful for projects that actually have 
proper release versions, or at least tag versions.

Then if the maintainer wants an easy version check they can grep the 
list for their packages, and if not, they can continue doing things they 
way they always have done.

regards, Tim

On 11/03/2025 06:46, 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'm not the only one who could possibly do it, but AFAIK I'm the only
> SBo admin who currently has the free time to possibly work on it. I
> don't want you to think "This guy doesn't want to do the work because
> he's lazy" or "because he's opposed to change".
>
> I just don't see it as being worth the time and effort. I don't think
> it would actually do much to prevent lazy maintainers from being lazy,
> and it would be marginally useful for active maintainers... but also
> annoying.
>
> If a human says "Hey, can you update <whatever> to version <v>?", I
> can respond with one of these:
>
> - "Version <v> is a development version, I prefer to stick with the
>   stable version"
>
> - "I will, when I have time to work on it, please be patient"
>
> - "I tried to update it, but it needs a newer version of <library> than
>   Slackware 15.0 has"
>
> - "I tested the newer version, and it has bugs that make it useless"
>
> - "<whatever> is a dependee for <other-build>, which requires the 
> older version"
>
> - "I have stopped using <whatever>, would you like to take over 
> maintenance?"
>
> If an automated email bot sends me such a message, I can't explain
> anything to it.
> _______________________________________________
> 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/
>


-- 
This email has been checked for viruses by AVG antivirus software.
www.avg.com