[Slackbuilds-users] Optional dependencies in info file

Willy Sudiarto Raharjo willysr at slackbuilds.org
Sun Nov 29 16:56:07 UTC 2015

> What do you think about putting optional (available from SBo)
> dependencies in the info file?
> I think that would allow for further automation.
> What I have noticed is that, it's sometimes hard to go through the
> README and spot all the optional deps, because everybody writes README
> as she/he sees fit.
> Also, I don't know how, but it could be possibly worth if all the
> variables (like ENABLE_FOO=yes, DISABLE_BAR=no) could be gathered in one
> well structured place.
> This thoughts came to me when I wanted to build 'ffmpeg'. Well, not all
> of those thoughts, because SlackBuild for 'ffmpeg' is actually well
> written.
> But if some more rigid structure, possibly easily understood by
> computers, was enforced, it could make users' life easier.
> What do you think?

It's really up to the maintainer to set which deps should go into
REQUIRES since he/she is the one knows best about it. We only make sure
that it builds normally with all the deps mentioned on the README.

my personal thought:
I like to keep the packages minimum and list all the optional ones in
the README. I don't want to have a bloated systems with all deps are
listed just to satisfy minor functionality

Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20151129/3db3cc2c/attachment-0001.asc>

More information about the SlackBuilds-users mailing list