[Slackbuilds-users] Intent for python SlackBuilds with SLKCFLAGS and LIBDIRSUFFIX

[fourtysixandtwo]

I stick to the template as much as possible and think it's best just to
leave them there.  They are just NOTE's and can be ignored as such, or at
least I do.  It's more work to add or remove them and I like the
consistency.

I diff my builds against the template as another check (one without the
extra comments) and it's much easier to note what should change or be
unique to each build.

And like you mentioned, mass edits are much easier which I found out doing
the i486 -> i586 changes.

That's my $0.02


On Wed, Sep 20, 2023 at 5:48 PM Jeremy Hansen <jebrhansen+SBo at gmail.com>
wrote:

> Since sbolint (from system/sbo-maintainer-tools) is being ran on github PR
> requests and newer versions of sbolint are catching when SLKCFLAGS and
> LIBDIRSUFFIX are not being used, are we expected to not include them on the
> SlackBuilds? If so, should we remove the entire if/then block for the ARCH
> detection since that's typically all it does?
>
> I ask because the templates for python SlackBuilds still include the ARCH
> detection block and I don't want to remove it from my SlackBuilds if the
> admins are expecting them to be there to simplify mass edits in the future.
>
> I imagine this also applies to other SlackBuilds, but have only noticed it
> so far with python ones. I expect there is a desire for consistency when
> possible, so I'd love some clarification!
>
> Thanks for everyone's work!
> Jeremy (aka bassmadrigal)
> _______________________________________________
> 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/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20230920/b2182d84/attachment.htm>