On Wednesday, November 12, 2014, Barry Grundy <[email protected]> wrote:
> I maintain a particular package, and it's due for an upgrade. I've been
> playing with one of the options to the package and Iv'e determined that for
> my use I would rarely run without that particular option.
>
> Is it bad practice to have the SlackBuild enable an option by default?
> Obviously the README would cover the subject. Basically I'm asking to turn
> an option into a "requirement".
>
> The package in question is bulk_extractor (already in SBo), and the option
> is liblightgrep (I'll be submitting the new SlackBuild concurrently).
>
> The .info would reflect the requirement, and the bulk_extractor README
> would indicate that the requirement could be disabled by removing
> "--enable-liblightgrep" from the SlackBuild.
>
> Is this kosher(ish)?
>
Why not set up a switch, on/off by default, say, so that the option can be
run/not run without editing the script:
LLG=yes ./blah.SlackBuild
This is done in a number of scripts (JDK, qemu, nvidia, ...)
--
You! What PLANET is this!
-- McCoy, "The City on the Edge of Forever", stardate 3134.0
_______________________________________________
SlackBuilds-users mailing list
[email protected]
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/
