-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jason Smathers wrote: > On 10/2/07, *Robin H. Johnson* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > Hi Guys, > > Before dberholz complains about my next commit, given that we have > support in profiles for package.use, how soon can we start to use it to > replace the old crufty no* flags (particularly ones that are > critical to > a system). > > > I like the default use flag solution, which seems to be introduced with > portage 2.1.2. This way you can replace nofoo with foo and > IUSE="+foo" if you want it to default on.
Given that >=sys-apps/portage-2.1.2 has been stable since February, and it's included in the 2007.0 release media, I think it's pretty safe to start using package.use in profiles. As for using things like IUSE defaults and SLOT dependencies in ebuilds (both supported by portage-2.1.2), the most backward compatible approach is to do an EAPI bump. We should probably include a few other things in the EAPI-1 bump [1] that aren't implemented yet. We don't have to include everything that's planned, but it would be good to include at least some of the simplest features. It's also possible to skip the EAPI bump for some of the implemented features and redefine EAPI-0 to include them, but that has backward incompatibility repercussions for users that lag months (or years) behind in updates. The negative impact of this approach lessens as the time since portage-2.1.2 stabilization increases. > When will the portage 2.1.0 and 2.1.1 ebuilds will be dropped? The old ebuilds are kept only as an upgrade path from older versions of python. People shouldn't use them for anything more than that. > With either solution, when updating existing ebuilds, how do you alert > users that they must change use flag nofoo to -foo if they want to > maintain nofoo functionality? One possible solution is for the ebuilds to support both flags during a migration period. If the ebuild detects that a deprecated flag is enabled, then it can issue an ewarn or eerror message to notify the user. Zac [1] https://bugs.gentoo.org/show_bug.cgi?id=174380 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.7 (GNU/Linux) iD8DBQFHAsZh/ejvha5XGaMRAghaAKDts+vXjyT3lqvR4QpGeUkR7a3pYACghgp0 XJFYeIG5CIQQKINzxtqHyXo= =iE9X -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
