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

[Jeremy Hansen]

On Mon, Mar 3, 2025, 10:34 PM Lockywolf <
for_slackbuilds-users_mlist_2023-04-21 at lockywolf.net> 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.
>

Looking over my SlackBuilds that package repackd binaries, I feel a
template is unlikely you capture the many nuances required in a repack.
Some are able to reside in /usr/ (discord), while others are better
contained in /opt/ (SweetHome3D, blender). Some may include .desktop files
while others will require creating and/or modifying them.

Basically, looking at your existing template, there is very little that
would work on the repacks I package.

On my sbgen.sh script¹, I just simply have an essentially "do you own
thing" template for situations like repacks where existing templates don't
work. It simply doesn't contain a compilation section and provides a
comment for maintainers to add their own commands. These scripts seem to
require a lot of manual really that is likely hard to capture on a single
template.

But maybe I just don't repackage enough software to realize there is a
solid template that applies to most rather than many requiring their own
unique commands...

Jeremy

¹https://github.com/bassmadrigal/scripts/blob/master/sbgen.sh

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250304/9acf64cd/attachment.htm>