-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brian Harring wrote: > On Tue, Aug 08, 2006 at 08:33:51AM +0100, Ciaran McCreesh wrote: >> On Tue, 8 Aug 2006 00:22:50 -0700 Brian Harring <[EMAIL PROTECTED]> >> wrote: >> | On Tue, Aug 08, 2006 at 07:23:31AM +0100, Ciaran McCreesh wrote: >> | > On Mon, 7 Aug 2006 21:41:39 -0700 Brian Harring <[EMAIL PROTECTED]> >> | > wrote: >> | > | > The use.force feature is complementary to use.mask. It's >> | > | > exactly the same concept, but inverted. >> | > | >> | > | And both files _should_ be implemented via use deps. >> | > >> | > Huh? How? >> | >> | forcing cxx on via package.mask for gcc >> | sys-devel/gcc[-cxx] >> | >> | forcing it off >> | sys-devel/gcc[cxx] >> >> Mmm. See, that'll lead to error messages if the user sets USE=cxx and >> then tries to install gcc. With the .mask/.force, it's handled >> automatically and indicated visibly by use flags being (parened). > > The error msg would be "blah is masked", with an explanation of why. > Pretty standard fair, portage already does the same now for non use > dep maskings.
It does seem appealing to unify the package.use.mask and package.use.force functionality into a single file that acts like package.mask with use-deps support. If we do it this way, devs won't be able to start using package.use.mask until a new implementation is ready. AFAIK Paludis already has support for separate package.use.mask and package.use.force, so they'd have to change their implementation to be compatible with the new unified format. > As is, the package.use.mask patch that got shoved in gives _no_ > indication that it's forcing a flag off for a pkg- leaves the user > wondering wtf occured once they spot the flag is disabled. > > Point there is that arguing against it based on UI code is a > non-arguement; either implementation (for portage at least) requires > mangling portage's -vp code to indicate the forced disabling/enabling. Some indication in the UI about flags being masked and/or forced would be nice, and prevent user confusion (as long as they understand the UI output). Zac -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFE2NCi/ejvha5XGaMRAvpaAKDghZnY4yI98yte0X88h6AjpPbsFgCePu6J x0WSvPuI/FO5Z41bgxdWLAQ= =NWMt -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list
