[Slackbuilds-users] sbotools maintainership?

[Slack Coder]

Why not keep it as sbotools3?  This way it is clear there was no hand 
over.  As a user, I would prefer to knowingly opt in to forks by people 
unaffiliated with the original project.

There also remains the problem of how does it relate to the project 
webpage which remains up?  Or what happens if pink-mist comes back, 
however unlikely?

On 11/20/24 07:35, K. Eugene Carlson wrote:
> On Wed, Nov 20, 2024 at 2:42 AM Shahab Vahedi via SlackBuilds-users <
> slackbuilds-users at slackbuilds.org> wrote:
>
>> What happens for the people who have installed sbotools3 package then?
>> Is there a plan to update both packages or sbotools3 package will silently
>> get no updates or removed?
>>
>> An intrusive approach could be updating the sbotools3 package for the
>> last time that replaces the whole content with a mere script that instructs
>> user to switch to sbotools package.
>>
> If sbotools3 is removed, it will report itself as an out-of-tree SlackBuild
> whenever the user runs sbocheck.
>
> On Wed, Nov 20, 2024 at 2:52 AM B. Watson <urchlay at slackware.uk> wrote:
>
>> Since there already is a sbotools3, I don't know what Eugene's got in
>> mind. Get rid of one or the other might be a good guess...?
>
> Yes, the plan would be to change the sbotools upstream and remove sbotools3
> from SBo. The original authors are thanked prominently on the website and
> in README.md, none of their attributions have been removed, and I'm
> retaining the WTFPL license.
>
> On Wed, Nov 20, 2024 at 6:43 AM Matt Egger <matt.egger at gmail.com> wrote:
>
>> I'm curious about the compat32 issue as well. What is that about?
>>
> In sbotools, ARCH=i486 is passed to the SlackBuild whenever a compat32
> build is requested (with e.g. "sboinstall -p"). This would have mostly
> worked when the feature was introduced, but in the 15.0 repository, almost
> all SlackBuilds default to i586 (or even i686) for 32-bit architecture.
> This results in build failure. I suspect the feature has never been
> particularly popular, since it would have caused problems for most builds
> even during the 14.2 cycle.
>
>
> _______________________________________________
> 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/
>