Mailinglist Archive: opensuse-buildservice (348 mails)

< Previous Next >
Re: [opensuse-buildservice] RFC: new repository scheduling options
  • From: Jan Engelhardt <jengelh@xxxxxxxxxx>
  • Date: Wed, 28 Apr 2010 15:20:36 +0200 (CEST)
  • Message-id: <alpine.LSU.2.01.1004281515250.2258@xxxxxxxxxxxxxxx>

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
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).

<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?
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups
References