Am Montag, 21. Dezember 2009 14:22:00 schrieb Petit Eric:
2009/12/21 Petit Eric
: you cannot "manage" this with the build and publish flags ? Perhaps at the end it will cost less time ? http://picpaste.com/pics/Capture-5.1261401374.png
Because my suggestion could be confuse here it is more details, idea should be to disable all build and/or publish, use an worksheet to list all order dependency, build the package at the highest level, publish it, once published, disable it again, build the second package, etc, then when all dependency packages are build, published and disable, enable all other packages.
this is a even more horrible workaround. Best solution is to reduce the cycles as much as possible. Working around the cycle handling only means that you have high chances to get broken packages. And if you don't know why the cyclces are there (or that many and large) you have also high chances to break your distro. If you know why they are there, you should be able also to break them for example via "Ignore:" statements in your project configuration in a valid way. as usual, this has absolut nothing to do with monoosc so it can't be used to solve the problem. bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org