On Sun, 15 Oct 2006 22:35:10 +0200 Jakub Moc <[EMAIL PROTECTED]> wrote: | > Which is why I suggested changing Portage's behaviour earlier in the | > thread. Like it or not, overlays are already getting complex enough | > that they'd benefit from profile behaviour. | | Because maintaining your own profiles and stacking them and dealing | with all the related mess is a _lot_ easier that sticking a + before | foo in IUSE. Right. ;)
You mean, than sticking a + before foo in IUSE in every ebuild, and ensuring that changes are kept in sync and consistent with the behaviour of every single existing profile. | > | Nearest I can figure, you're pressing hard for the view that all | > | USE flags must come from profiles (by extension user | > | configuration); | > | > Yup. Default USE flags are profile dependent data. The sensible | > default value varies depending upon conditions like arch and system | > role. | | You are really circular, fix your record player :P That's not even remotely circular. They're profile dependent, so they belong in the profile. There is no circular. | Defaults that makes sense in profiles can and will stay there and | noone's damn forcing you to change it. We are talking about | per-package (or per-ebuild even) stuff here, which is a feature that | has been missing for ages. Which is solved quite happily in the profiles by package.use, and without the problems associated with the IUSE solution. | Sigh... You know Jakub, you'd be a lot less stressed if you sat down and thought about what was being discussed before posting. -- Ciaran McCreesh Mail : ciaranm at ciaranm.org Web : http://ciaranm.org/ as-needed is broken : http://ciaranm.org/show_post.pl?post_id=13
signature.asc
Description: PGP signature
