[Slackbuilds-users] Package as a whole or in different parts

Jeremy Hansen jebrhansen+SBo at gmail.com
Tue Jan 30 21:19:26 UTC 2018

On Tue, Jan 30, 2018, 1:43 PM B Watson <yalhcru at gmail.com> wrote:

> On 1/30/18, Xavier Maillard <xavier at maillard.im> wrote:
> > As I do not want to go the wrong way and I want to stick with the
> > KISS philosophy, I am just asking here: how would you package this
> > ? As a whole sat SBo build script, as 2 SBo (one for the backend
> > and one for the frontends), as many different SBo scripts (one for
> > the backend and one per frontend) ?
> Does the source for all of the above come as a single tarball?
> If so, I might do a single SlackBuild, that builds the backend and
> all the frontends by default, with environment variables to disable
> parts of it.
> Example: the transmission SlackBuild. I maintain that one, though I
> didn't write it from scratch (took it over from previous maintainer a
> while back).
> If the sources ship separately, it makes more sense to do separate builds
> for the different parts.

I do a similar thing for mediainfo. It is the same source for both the CLI
and GUI versions, so I have the CLI enabled by default (but can be disabled
if desired) and the GUI optional by passing GUI=yes.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20180130/ed49c45f/attachment.html>

More information about the SlackBuilds-users mailing list