On Fri, 13 Apr 2007 11:52:16 -0400 Mike Frysinger <[EMAIL PROTECTED]> wrote: > > > you're proposing we suddenly bloat all of our src_install > > > functions for no gain at all ... sounds like a no brainer to me > > > > No, I'm proposing that functions not have strange side effects. > > the behavior here is desired ... you install into a directory, then > the directory should exist
These fail: cp somefile dirdoesnotexist/ mv somefile dirdoesnotexist/ ln -s somefile dirdoesnotexist/ dohard somefile dirdoesnotexist/ mkdir dirdoesnotexist/newdir This succeeds: dosym somefile dirdoesnotexist/ > > Well no, they can't, because there are a whole load of ebuilds that > > will break if they do that. But if it's introduced as mandatory > > (barring ebuilds RESTRICTing it) for EAPI 1, the tree will slowly > > move towards everything that reasonably can do having working test > > suites, which will be a huge step forward for QA. > > that's really the QA's job to enforce, not the package manager > > if the QA team wants to spear head a tree wide effort at getting > src_test up and running, they're certainly free to The arch teams have been pushing for this for a long time. They're trying to get this enforced, but are having limited success because there's no way for FEATURES=test to become widely used that won't lead to broken user systems. Moving src_test to be always on in future EAPIs is an easy way of helping arch teams achieve this goal without breaking anyone's system in the meantime. -- Ciaran McCreesh
signature.asc
Description: PGP signature
