On 23.10.2016 12:36, Andrzej Telszewski wrote:
On 23/10/16 01:56, Christoph Willing wrote:
Who is going to decide REQUIRED vs OPTIONAL for the many (I suspect) non
obvious cases? Presumably the maintainer. If a maintainer's balance of
REQUIRED/OPTIONAL deps doesn't suit someone else's particular
needs/wants, then the builder will have to change their personal .info
files anyway (or complain to the maintainer).
I think the problem of REQUIRED vs OPTIONAL has been solved long time ago.
It's the maintainer that decides what is placed in REQUIRED and most
probably 99% of us just installs what is there.
And most probably 99% of the time what is placed in the REQUIRED is what
is ABSOLUTELY necessary to compile the software or to run it (run time
dependency).
Everything else, i.e. things that could be added later on or are
detected during compilation, are OPTIONAL.
I'm the supporter of the OPTIONAL field and I actually proposed it
sometime ago, but it was rejected too.
I think there is too big resistance here for this addition, because
naturally it would involve work.
I think maintaining Options in README is about the same work as
providing an Options field in the Info-file.
Looking at https://slackbuilds.org/repository/14.2/multimedia/ffmpeg/ ,
it felt much better to see this list in in an OPTIONAL field in, which
would also be parsable by tools like sbotools.
Without further bothering the qemu-maintainer, whatever package requires
qemu compiled with usbredir, then could have something like
REQUIRED="qemu:usbredir" in the Info-file.
Johannes
_______________________________________________
SlackBuilds-users mailing list
[email protected]
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
