[Slackbuilds-users] sbotools maintainership?
B. Watson
urchlay at slackware.uk
Wed Nov 20 03:58:09 UTC 2024
On Tue, 19 Nov 2024, K. Eugene Carlson wrote:
> The current maintainer has been inactive on SBo for about the same amount of time. I sent him an email about two weeks ago asking permission for a maintainer change, but he hasn't
> gotten back to me. Effectively, this would mean renaming my fork, sbotools3 (which is due for a version release either way), to sbotools and continuing development and maintenance
> under that name. Would this be all right?
If you haven't heard back in 2 weeks, it's yours.
If you replace the original source with your own fork, that's
perfectly OK too: it's your build, you do what makes sense to you.
You don't have to rename your source. You can keep the SBo package
named 'sbotools' and use something like SRCNAM=sbotools3 for the
tar/etc commands in the script.
I'd suggest putting a line in the README explaining that the build is
for your 'sbotools3' fork, which is actively maintained.
More information about the SlackBuilds-users
mailing list