On Thu, 7 Apr 2005 22:20:43 +0900 Jason Stubbs <[EMAIL PROTECTED]> wrote: | Back in my quest to rid the tree of the evil virtuals and their plot | to destroy my mind. I think I've covered all bases with this one - | perhaps even enough to satisfy TGL. Take your best shot!
1) You need an explicit example of what virtual/jdk/jdk-1.4.ebuild looks like. 2) For the consistency section, I'm not sure how you're going to implement this. The example I tend to use is this (versions simplified slightly for clarity): * User emerges vim-6.3, gvim-6.3. ~vim-core-6.3 is in as an RDEPEND. * User upgrades to vim-7.0. ~vim-7.0 is in as an RDEPEND. * User still has gvim-6.3 installed. gvim-6.3 has an RDEPEND upon ~vim-6.3, which is no longer installed. gvim is now broken. An example of exactly how portage would 'solve' this would be helpful. Would it ask for an unmerge of gvim-6.3 or would it include an upgrade of gvim-6.3 as part of the "emerge ~vim-7"? 3) We don't specify every virtual in every profile thanks to cascades. 4) Backwards compatibility -- all virtuals ebuilds should include DEPEND=">=portage-2.whatever" as well as the "|| ( foo bar )" stuff. 5) Someone tie up TGL and don't let him escape until he agrees to be a dev this time. -- Ciaran McCreesh : Gentoo Developer (Vim, Fluxbox, shell tools) Mail : ciaranm at gentoo.org Web : http://dev.gentoo.org/~ciaranm
pgphASILb0L5Q.pgp
Description: PGP signature
