[Slackbuilds-users] Optional dependencies in info file

Christoph Willing chris.willing at iinet.net.au
Sun Nov 29 23:31:34 UTC 2015

On 11/30/2015 09:11 AM, Andrzej Telszewski wrote:
> On 29/11/15 23:56, Christoph Willing wrote:
>> The only work is adding the options you want but that is also the
>> advantage - you have the options _you_ want rather some some arbitrary
>> set of options the maintainer wants or believes end users will want.
> Actually, it's like that at the moment and it always will be like that.
> I mean you will always have some choices that you can or not adjust to
> your needs.
> The difference is that "optional options" are mentioned in README,
> whereas "required options" are placed in info - you put the optional
> deps in *.info, which gives the whole thing better structure.
> But it is always *YOU* who has to make the choice, the difference is how
> the information about possible dependencies is given to you.

We need to bear in mind the difference between options and dependencies. 
An added option may, or may not, entail an added build dependency i.e. 
any added ENVOPTS (or whatever) field _may_ need adjustment to the 
REQUIRED field too. In order to keep existing .info fields pristine, I 
use an additional PREREQS field to keep track of additional 
dependencies, leaving the REQUIRED field intact.


More information about the SlackBuilds-users mailing list