Am Mittwoch, 28. April 2010 15:20:36 schrieb Jan Engelhardt:
On Wednesday 2010-04-28 15:10, Adrian Schröter wrote:
And we would like to hear some feedback about them.
I'm gonna love this..
The values of the attributes can be these:
<define ns="" name="rebuild-modes"> <choice> <value>transitive</value> <!-- DEFAULT: build on source change and all depending packages including indirect dependencies --> <value>direct</value> <!-- build on source change and direct depending packages --> <value>local</value> <!-- build on source change only --> </choice> </define>
It should be possible to specify exceptions on a per-package basis. I
maybe later, for now this is out of focus.
would set a project to "direct", but to cater for packages using static inclusion of a library (prog -> foo.a), one may need "transitive" in case the library changes as a result of a rebuild (like when it uses __DATE__, though that's a light example; there is probably someone doing worse things that change just because of a rebuild).
there is also other modes thinkable like "build on provides changes", but this is also future. However, it should be no problem to add new modes by this design.
<define ns="" name="block-modes"> <choice> <value>all</value> <!-- DEFAULT: block until all packages we depend on are built --> <value>local</value> <!-- like all, but ignore packages from other repositories --> <value>never</value> <!-- immediately start building the packages --> </choice> </define>
What happens if projects have a cyclic linking against another?
I hope to catch via a cycle detection. Howver only implemented for 50% yet. -- 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