[Slackbuilds-users] sbotools maintainership?

[Matt Egger]

On Wed, Nov 20, 2024 at 7:35 AM K. Eugene Carlson <kvngncrlsn at gmail.com>
wrote:

> 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.
>
> Thanks for the explainer. One of my slackbuilds does default to i686 on
32-bit, so I appreciate this fix.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20241120/835436d4/attachment.htm>