Re: Options vs. Binary packages

["Blair Sadewitz" <blair.sadewitz%gmail.com@localhost>]

Lately in my mk.conf I've been using PKG_DEFAULT_OPTIONS.<pkgsrc-category>, e.g.
-nas -arts esound jack for PKG_DEFAULT_OPTIONS.audio.  What I envision
[roughly] is starting with groups like this, then definition
"meta-options", i.e a "whole pkgsrc option".  A meta-option for gnome
is a prototypical example.

Another approach would be to simply decrease the number of options in
many packages, instead making them mandatory.  For instance, consider
ffmpeg; IMHO it's better to build it with most of the optional
packages included by default.  This would be termed the 'supported
configuration'.  This strategy seems apt for promoting harmonious
(API/ABI compability, for example) [inter]dependencies.

Regards,

--Blair