-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thomas de Grenier de Latour wrote: > On 2008/08/02, Zac Medico <[EMAIL PROTECTED]> wrote: > >> USE flags are something that can be enable or disabled > > Here, what the flag would enable/disable is belonging of live packages > to the @live-rebuild set. Compared to the RESTRICT solution, user > gains an easy per-package control of this set (sure, the flag would be > turned on in profiles, so that @live-rebuild is complete by default). > >> but the behavior of the src_unpack() method downloading live sources >> is not something that's generally controlled by a USE flag afaik. > > Right, this "live-rebuild" USE flag would not control anything in the > way the ebuild is executed, but only in the way the package is handled > by Portage. It's not primary usage of USE flags, sure, but it's not > completly unusual neither (for instance, take USE flags which are just > there to trigger some convenience PDEPEND). > > > Anyway, to rephrase / summarize my idea: > > - IUSE="live-rebuild" in the ebuild > ==> triggers LIVEVCS.stable repoman check > > - IUSE="live-rebuild" in the ebuild, and package is installed, > and USE flag "live-rebuild" is enabled for this package > ==> makes it belong to the @live-rebuild set >
It seems like USE would be an unconventional location to store that information and I'm not sure that it really belongs in the ebuild. Shoehorning it into package.use might have some benefits but USE flags are conventionally used to control ebuild behavior rather than package manager behavior. Perhaps some separate user config file would be more appropriate for that purpose. Zac -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkiVHLoACgkQ/ejvha5XGaOq4QCeMZOJcHKn2d2LzhIeRmGrLjlu 2J8An1C1lpC5VsCPqnwz4kpPBVEFFRDE =M6Pf -----END PGP SIGNATURE-----
