[Slackbuilds-users] [RFC] a binary repack SlackBuild template.

[Antonio Leal]

I think its a valid proposal. The end-user will know immediately he is 
going to get something not build from source. A template could be a good 
idea, but I wouldn't enforce its application too strongly, maybe present 
it as a suggestion?

If adopting this, *when* would it be done? Isn't there a risk that 
unaware users stay with old packages, without any update?  So if 
changing, I would say it better do it when -current is released and all 
scripts are revisited.

<joking>  If we're going the Aur way why not "-git" too? </joking>


On 3/4/25 6:29 AM, Lockywolf wrote:
> Dear SlackBuilds community,
>
> Increasingly, we have to write more and more binary repacks,
> as software is becoming harder and harder to build on the premises.
>
> While this is an unfortunate development, and the community members
> are encouraged to build software from the original sources to ensure
> transparency and flexibility, sometimes building a package as a
> repack is an unnecessary evil.
>
> This message has (attached) a proposed binary-repacking SlackBuild,
> which I would like to propose for an inclusion into the templates
> repository.
>
> Please comment and suggest how this template can be improved.
>
>
>
>
> _______________________________________________
> 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/20250323/0f5a2144/attachment-0001.htm>