On Wed, 11 Jun 2008 00:11:32 +0200 Bo Ørsted Andresen <[EMAIL PROTECTED]> wrote:
> On Tuesday 10 June 2008 18:26:55 Doug Goldstein wrote: > > Let's try to aim to do an EAPI=2 sometime soonish since Portage now > > has USE flag depends in version 2.2 which is looming on the > > horizon. It'd be nice to hit the ground running with supporting > > these. I know it'll be trivial for the Paludis and pkgcore guys to > > make this work since they already support USE flag depends. > > I would like the portage devs to comment upon which of the following > features they think could easily be implemented before portage 2.2 > goes stable. There's still some time since it hasn't left > package.mask yet, so I'd rather they exclude the features that will > take too long to implement than anybody else doing that... Well, actually I would rather not add any new features between pre8 and rc1 to not further delay 2.2. And generally I'm also not in favor of adding new features during the rc phase as it's there to eliminate remaining bugs and for refinement of existing features, not to add new unknowns. > Already implemented: > - Use dependencies, it's not clear to me whether we all agree > entirely upon the syntax yet though (bugs #2272 and #174406) > > Things I believe should be trivial to implement: > - Custom output names in SRC_URI, also called arrows (bug #177863) This I'd definitely delay as it probably affects a number of things. > - Guarantee trailing slashes (bug #174408) Mostly a matter of finding the relevant spots, the actual work to implement it would be trivial. Could be considered as bugfix. > - Limit values in $USE (bug #176467) Also requires little actual work, question is only if this should be enabled for EAPI=0/1 as well, and how it relates to USE_EXPAND and ARCH. If it should be done for existing EAPIs as well could be considered as bugfix. > - doins support for symlinks (bug #179932) If someone implements it it can be included (do you want an EAPI bump for that?) > - Enable FEATURES=test by default (bug #184812) Only if >99% of the stable and ~arch tree and all potential "system" packages build with it (IOW: no) > - GLEP 42 - news items Already implemented. > Bigger features I'm interested in: > - Making do* die on failure by default (without changing their > behaviour for previous eapis). Possibly adding either nonfatal or > try_do* for cases where this isn't desired. (bug #138792) > - More phases > - src_prepare, for applying patches and running autotools etc. > - src_configure, for running configure scripts (bug #197859) > - pkg_pretend (bug #177860 - could also be used to fix bug #75936) > - maint_*, it's not clear to me if this has been fleshed out in > sufficient detail yet (bug #185567) Unlikely for 2.2. > - default_*, allows an ebuild to redefine phases to add more > functionality and then call default_$phase. Currently the default > phases are lost when redefining the phases. Should be trivial to implement off-hand (just converting the existing defaults to wrappers) > - default for src_install (bug #33544) Should also not be terribly difficult, though I'd rather wait until after 2.2 final. > - Ranged dependencies (bug #4315) Unlikely for 2.2. > Of course I'd like GLEPs 54 and 55 too but since the council still > hasn't made a decision about them I'll leave them out.. Well, I already said everything about those during the first discussion round and the relevant council meeting. Marius -- Public Key at http://www.genone.de/info/gpg-key.pub In the beginning, there was nothing. And God said, 'Let there be Light.' And there was still nothing, but you could see a bit better.
signature.asc
Description: PGP signature
