Seems like use.force might be a bad name..... when I first read the email, and saw use.force, the first thing that came to mind was "gentoo forcing something?" and even after reading the email, I wouldn't expect to be able to override something that was "forced." I'm not sure what a better name would be, but I think there may be one...
also, wouldn't the override be in use.unforce? >_< On 6/13/05, Simon Stelling <[EMAIL PROTECTED]> wrote: > Sven Wegener wrote: > > We just had a short discussion over in #gentoo-portage and the idea of > > an use.force file for profiles came up. It allows us to force some USE > > flags to be turned on for a profile. It's not possible to disable this > > flag by make.conf, the environment or package.use. But we would not be > > Gentoo, if we don't leave a backdoor. You can disable the flag by > > putting -flag in /etc/portage/profile/use.force if you really need to. > > Same goes for sub-profiles that need to disable this flag. > > Yay! > > > I gues use.force has some other places where it is useful. Like the > > default-darwin profiles which use ARCH="ppc" and USE="ppc-macos" but the > > ppc-macos flag can be removed by using USE="-ppc-macos" in the > > environment. Or selinux profiles, to force the selinux flag to be turned > > on. > > It'll be also very useful for the amd64 profiles as in 2005.0 the use > flag 'multilib' is disabled but multilib-support is forced. (There are > no-multilib-profiles though.) > > > Comments? > > I consider use.force very useful, it'll finally make all the amd64 users > stop asking themselves why the documenation says they will get multilib > but the use flag is disabled, so please, go ahead implementing it. > > Regards, > > blubb > > -- > Simon Stelling > Gentoo/AMD64 Operational Co-Lead > [EMAIL PROTECTED] > -- > gentoo-dev@gentoo.org mailing list > > -- gentoo-dev@gentoo.org mailing list
