Sometimes I get errors that sounds like they should have been detected before the ebuild was submitted, like two packages that tries to go into the same slot. I'm not sure how an ebuild is tested, but what about having say a few machines (virtual?) that has EVERYTHING installed? And some of the machines could use a lot of ~x86 (or other ARCH) to get newer packages. And if all devs are using these machines for automatic testing will that not make it even more likely to find bugs? IMHO this ought to catch a few bugs with the ebuilds. Reproducible: Always
Not possible. Even if it were, it wouldn't be feasible.
(In reply to comment #0) > And if all devs are using > these machines for automatic testing will that not make it even more likely to > find bugs? > IMHO this ought to catch a few bugs with the ebuilds. Something that intend to provide similar pre-"submission" checking facilities is the AutotuA project. It's purpose is described here: http://git.overlays.gentoo.org/gitweb/?p=proj/autotua.git;a=blob;f=PURPOSE;hb=HEAD Homepage should be http://soc.gentooexperimental.org/projects/show/autotua Git repository viewable online at http://git.overlays.gentoo.org/gitweb/?p=proj/autotua.git;a=summary with the clone command needed to get this to local machine shown nicely on that page too. Maybe you'd like to help out with that project, contribute to it, etc? The current people working on it hang out at #autotua in irc.gentoo.org (currently FreeNode) IRC network.
Well, that's mostly what I do at the moment. Can't have all packages installed, but a stage3 + binpkgs is fast enough to get each package compiled once in ~10 days initially, incremental building after that is faster (~2-3 days it seems) Just needs people with nice hardware who are willing to file a metric ton of bugs! (Feel free to ask me for advice how to handle it)
(In reply to comment #2) > (In reply to comment #0) > Maybe you'd like to help out with that project, contribute to it, etc? I will try to read about it and see if it is completely out of my league or if there is something I can do.
*** This bug has been marked as a duplicate of bug 473 ***
