[Slackbuilds-users] SlackBuild Ettiquette

Bojan Popovic bocke at mycity.rs
Thu Nov 13 09:00:03 UTC 2014


Well that's why many SlackBuilds have optional switches. You can choose
whatever you want from the command line

 OPT1=YES OPT2=NO ./package.SlackBuild

or in a sbopkg queuefile:

 package | OPT1=YES OPT2=NO

In there are optional switches, then it's not really important what
defaults the maintainer chose.

My 2,5 cents.


On Thu, 13 Nov 2014 14:13:22 +1000
Christoph Willing <chris.willing at iinet.net.au> wrote:

> For many softwares, optional features are either set or unset by
> default in the configuration script supplied with the source code. In
> accordance with the general Slackware practice of leaving upstream
> alone as far as possible, I would suggest that the default values you
> choose for options should be whatever are the defaults in the
> software itself, _not_ what you happen to use yourself.
> Its quite annoying when SlackBuilds choose options contrary to the 
> upstream defaults. One SlackBuild that springs to mind immediately
> turns off an option that is on by default just because the maintainer
> himself doesn't use the facility provided by that option. Having it
> turned on wouldn't force him to use the facility provided by the
> option but he's actually added code to the SlackBuild to turn it off
> anyway.
> chris

More information about the SlackBuilds-users mailing list