[Slackbuilds-users] Script submission technicality
fsLeg
fsleg at t-rg.ws
Wed Jan 15 18:42:22 UTC 2025
I just realized something. Anyone can submit a SlackBuild. There's no
authorization, no checks who actually submits it, and even Submission
Guidelines don't mention anything about who can submit SlackBuilds. Even
existing ones. So while it would be a good courtesy to notify some
script's author that a new version came out or there's a bug in their
script, you could just fix it yourself and submit it without changing
author and maintainer fields. If it's a good-willed change, you just
specify your own email when submitting a tarball. If you're slightly
less good-willed, but still want the SlackBuild to just work, you can
specify the maintainer's email, and it doesn't even matter since it
seems that nothing is actually emailed when you submit a script.
So does it mean that it's actually OK to submit updates, fixes and
changes to existing SlackBuilds yourself if their maintainers don't do
it in reasonable time? At what point would that be considered a
takeover? Or is this just an oversight in the guidelines?
And side question, since I mentioned a takeover. I emailed maintainers
of two SlackBuilds and asked them to update their scripts, but got no
response in two weeks by now. How long should I wait before asking here
to take over their SlackBuilds?
More information about the SlackBuilds-users
mailing list