As discussed on the gentoo-dev mailing list, I have added the new global "USE" flag "emboss". This flag will be enabled by default and provided by "sci-biology/emboss". I made the necessary modifications to the base profile and to all x86 profiles (except hardened, selinux, embeded, uclibc and obsd). I have not modified any ebuild to make use of the new flag yet. Could the ppc and ppc-macos teams modify their profiles (except ppc64) to add "emboss" to the default "USE" flags defined in "make.defaults" and also add "emboss sci-biology/emboss" to "use.defaults"? Could all the other arch teams (and ppc64) modify their profiles to add "emboss" to their "use.mask"? I have no idea what the hardened, selinux, embedded, uclibc and obsd profiles managers should do, but I am sure they know. Thanks,
ppc 2004.3 and 2005.0 set
Asking on behalf of embedded and hardened and base. Why should this flag be enabled by default?
On behalf of ppc-macos, I ask the same question as hardened. Why should this be enabled by default? Most people are not going to want emboss as far as I know...
Added to use.mask on hppa.
use.mask on all mips, sparc profiles for now. If we keyword later we can always remove the mask...
What enabling "emboss" by default will do, and why I think we should enable it by default: Adding "emboss" to the default "USE" flags will not force the installation of EMBOSS. This is comparable to KDE: the "kde" "USE" flag is enabled by default in x86 (and other) profiles (e.g. "default-linux/x86/2005.0"), but KDE is not forced on any user. If "emboss" is enabled by default, EMBOSS will simply be installed as soon as a package has an optional dependency on it, unless the user explicitly disables EMBOSS support. The reason why I think "emboss" should be enabled by default is that the vast majority of users of packages such as aaindex, CUTG, PRINTS, Prosite, Rebase and TransFac want/expect EMBOSS support for these packages. (These are the only packages with optional EMBOSS support.) For example, although a minority of users have custom scripts to query the Prosite database, most will use the EMBOSS program "patmatmotifs" to interface with it, so having this program available when Prosite is installed is a sensible default. This is analog to why "arts" is enabled by default in many profiles, including x86: Most users want aRts support in their KDE applications, so making sure this support is enabled by default as soon as a package supports it seems reasonable. It will also allow me to get rid of the "no-emboss" local "USE" flags I had to use (since we have no means to enable a local flag by default). If I am not clear of if I missed something, please tell me. :)
solar@simple profiles $ grep -v ^# uclibc/parent | grep -v ^$ ../base solar@simple profiles $ grep -v ^# hardened/parent | grep -v ^$ ../base solar@simple profiles $ grep emboss base/use.defaults emboss sci-biology/emboss Nothing for embedded or hardened todo here and adding it to make.default would be silly.
macos inherits from default-darwin, and default-darwin inherits from base, so it seems we're all set too. Let me know if I'm wrong about that.
j4rg0n: The macos profiles are OK for "use.defaults" which they inherit from base, but the "USE" variable in "make.defaults" still needs to be modified since it is not defined in either base or default-darwin. I think the correct place to set this (if I compare with other cascading profiles such as x86) is directly in the 10.3 and 10.4 profiles. There is another macos profile named progressive, but I have not idea what it is for...
osx: See comment #9
use.mask-ed on alpha/arm/ia64
As requested, added to make.defaults
No response from amd64 or bsd. I added to "emboss" to "use.mask" on amd64.
Just so you don't think we were ignoring you, the reason you didn't get a response from us BSD folk is that our profile isn't even in the tree. There is an old deprecated flat profile for openbsd that g2boojum created ages ago, but the openbsd port isn't even active anymore (I think Grant was the only one working on it). -Cheers
