Rémi Cardona wrote: > I'll speak up then :) > > What I _really_ would like to see ASAP : > > 1) Dropping digest-* files for real (ie, not even having them on the > master rsync server and CVS) > > 2) Slotted deps (I had the feeling we were really close to having this a > while back, and then radio silence, maybe I missed the final announcement?) > > 3) USE-deps
Ok those interesting. > As for the politics behind the naming of the EAPI, where it should be > placed in the ebuild, whether it should be in metadata.xml or in the > filename, I don't really care that much. I'm thinking about having them embedded in the comment as first line as something like #!/usr/bin/env emerge --eapi $foo or # EAPI=$foo IFF we want to consider single ebuilds, but since I don't like the approach at all here another proposal: I'd rather have a way to sync the tree so that: - if your pm supports all the features you get the tree - if your pm doesn't you get a minimal tree that let you update to the newer one. That means having a way to maintain a branch with just system and the update path and have a way to put eapi versioning per tree. This solves pretty much the root problems: "do not have the package manager break on tree update" and "have a way to update the package manager from an ancient setup w/out unpacking a newer stage on it (that could be yet another solution)" Feel free to flame/decostruct this proposal as you please. lu -- Luca Barbato Gentoo Council Member Gentoo/linux Gentoo/PPC http://dev.gentoo.org/~lu_zero -- [EMAIL PROTECTED] mailing list
