> As far as I understand, SBo's policy is to only list strict dependencies > in the REQUIRES="" field. Those dependencies that are not strictly > necessary are eventually listed in the text, but not as strict > requirements. > > The VLC SlackBuild seems to be an exception to this policy. It lists an > impressive list of dependencies, but only a fraction of these are > actually strict dependencies. > > Suggestion: only list strict dependencies in the REQUIRES="" field, and > list all the extra dependencies in a separate text in the README? This > would spare the hassle of building jack-audio-connection-kit, avahi, > freerdp, etc. just to have a basic VLC.
Mandatory requirement is a must in REQUIRES, but if the maintainer thinks that a certain dependencies are needed in REQUIRES as well, it *may* be listed too (please give a good argument on the comment section during submission) ffmpeg in the past also includes lame, which was an optional dep. Of course, we don't want to have a bloated package, so it must be used with extra care. It's decided case-by-case. -- Willy Sudiarto Raharjo
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 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/
