On Sun, 2005-11-20 at 11:55 -0800, Michael Marineau wrote: > However changing this will also lead to many supprises and tick off many > users who don't know why a bunch of flags just vanished. How about we > leave the feature in portage but remove auto from USE_ORDER in the > 2006.0 profile and put a note about the changed behaviour the release > announcements. For users who do like the functionality just properly > document the existance of USE_ORDER in the install guide.
*applauds* Sensibility as well as an un-breaking upgrade path! Finally we see thought in this area ; ) Documenting this would be great. However, I'd -also- want the IUSE="+auto -bongodrums alpha beta +zeta" to be set, perhaps with a new USE_ORDER variable ":ebuild:" ? The dark magic was a very good and usable approach, however with the growth of our tree, it has seen its use and it may well be time to phase it out in favour of a more fine-grained mechanism. Adding and documenting a "recommended enable" set, would be a great start. It could also be used to fine-tune packages for the GRP set, in order to do partial on/off settings based on the parts that the maintainers consider "good and reasonable" I know one place where I'd love to see this is fex. the various multimedia backends, openssl/gnutls among other such settings. //Spider -- begin .signature Tortured users / Laughing in pain See Microsoft KB Article Q265230 for more information. end
signature.asc
Description: This is a digitally signed message part
