[Slackbuilds-users] Source code missing for some Slackbuilds scripts
Luveh Keraph
1.41421 at gmail.com
Mon Mar 10 19:18:24 UTC 2025
Yesterday I was building a bunch of packages in a system to match what I
have in a separate system. As it happens, a substantial number of them -
like e.g. calc, makemkv, monitorix, transcode, pari) could not be built
simply because the source code to be used is not available in the target
location any more.
For the most part it is not a big deal, for the new sources can usually be
found without a problem (things for transcode were a bit more tricky) and a
simple modification to the corresponding Slackbuilds script gets things
built properly. I was wondering, however, whether it would be a good idea
to add small script to the Slackbuilds repository whereby the script
attempts to download the source code for each item in Slackbuilds once a
day every day, and sends a warning email to the maintainer of each package.
This does not guarantee anything, as some maintainers simply stop checking
their emails, or even delete their email address, but I wonder whether it
would help those who still do maintenance chores, especially when they are
responsible for more than just a couple of items.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250310/46acf142/attachment.htm>
More information about the SlackBuilds-users
mailing list