Greg Freemyer - 15:44 3.12.13 wrote:
On Tue, Dec 3, 2013 at 3:31 PM, Michal Hrusecky <mhrusecky@suse.cz> wrote:
Greg Freemyer - 13:51 3.12.13 wrote:
...
Agreed that it is a nicety. When it was first proposed, my first thought was no way. Just the effort of creating all those staging projects would be rediculous. Then I thought about how efficient it would be to use BtrFS snapshots for that step and I changed my mind.
BtrFS cannot help to create more staging projects more easily. Staging project is OBS project containing package and rebuilding whatever depends on the package. OBS project is some little data but mostly metadata in some database. Staging project is NOT a directory.
Okay, that surprises me. I assumed every package had a directory somewhere that held the tarball, spec, patches, etc.
It probably has as well, don't know about the internals that much, but staging project contains mostly metadata that needs to be interpreted, it can't live just without OBS.
If that isn't the case, how resource intensive is it to create a staging project? and to run thru the dependancy analysis to see what needs to build? The compiles themselves get pushed out to the build farm and I suspect OBS has the capacity for that part of the extra load.
Creating and calculating dependencies is not that big problem, main problem is waiting to get scheduled and waiting for an empty worker I would say. And to wait for all dependencies to get built. In general with infinite build power, it should be possible to create a staging project for everything. But in the real world, I would prefer using some rule of thumb. -- Michal HRUSECKY SUSE LINUX, s.r.o. openSUSE Team Lihovarska 1060/12 PGP 0xFED656F6 19000 Praha 9 mhrusecky[at]suse.cz Czech Republic http://michal.hrusecky.net http://www.suse.cz -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org