[Slackbuilds-users] Optional dependencies in info file

[Andrzej Telszewski]

On 29/11/15 18:41, Petar Petrov wrote:
> do you suggest that all dependencies are listed in the REQUIRES field or
> that there is a new field eg OPTIONAL introduced?
>
> for example in case of EMBOSS:
>
> REQUIRES="jdk"
>
> OPTIONAL="clustalw primer3"
>
>
>
> 2015-11-29 19:10 GMT+02:00 Andrzej Telszewski <atelszewski at gmail.com
> <mailto:atelszewski at gmail.com>>:
>
>     On 29/11/15 17:56, Willy Sudiarto Raharjo wrote:
>
>             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
>
>
>     Well, your the boss;)
>
>     What do you mean by bloated system? If the optional deps are placed
>     in the info file, then automated tools can benefit from that. It's
>     still up to the user to decide if she wants them.
>
>     Putting optional deps in info makes just for easier processing, I
>     don't see any possibility of bloating here.
>
>     And SBo maintainers could declare that optional deps are not tested.
>
>     What do you think?
>
>
>
>
>
>         _______________________________________________
>         SlackBuilds-users mailing list
>         SlackBuilds-users at slackbuilds.org
>         <mailto:SlackBuilds-users at slackbuilds.org>
>         http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>         Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>         FAQ - http://slackbuilds.org/faq/
>
>
>
>     --
>     Pozdrawiam,
>     Best regards,
>     Andrzej Telszewski
>     _______________________________________________
>     SlackBuilds-users mailing list
>     SlackBuilds-users at slackbuilds.org
>     <mailto:SlackBuilds-users at slackbuilds.org>
>     http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>     Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
>     FAQ - http://slackbuilds.org/faq/
>
>
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
>

I meant something like OPTIONAL="clustalw primer3".

-- 
Best regards,
Andrzej Telszewski