[Slackbuilds-users] Source code missing for some Slackbuilds scripts
B. Watson
urchlay at slackware.uk
Tue Mar 11 06:46:23 UTC 2025
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.
More information about the SlackBuilds-users
mailing list