Mailinglist Archive: opensuse-buildservice (266 mails)

< Previous Next >
Re: [opensuse-buildservice] recursive project reference
  • From: John Kelly <jak@xxxxxxxxxxxx>
  • Date: Thu, 20 Nov 2008 08:37:55 +0000
  • Message-id: <200811200837.mAK8boQD019888@xxxxxxxxxxxx>
On Thu, 20 Nov 2008 09:13:21 +0100, Adrian Schröter <adrian@xxxxxxx>

If I use a recursive project reference, is OBS smart enough to break a
loop, or will it explode?

Yes, it does break a loop. But it really hurts the scheduler and our logs.
And it does make absolut no sence to have a setup like this. When you need
anyway both repos, you can put them together in one project.

What I need is not so simple. As I posted earlier, I want to build a
rollup release including all updates, plus my own package hacks, and I
want to bootstrap the whole thing from source.

Somewhere the docs say the current project is searched first. That
may be true for dependencies, but through trial and error, I learned
that's false for the package itself. When it's already built, and you
manually trigger a rebuild, hoping to bootstrap it against itself,
that does not work. OBS searches down the chain, and ignores the
package in the current project.

After trying different ideas, I can see OBS was not designed with the
idea of easily building a rollup release.

I'm still puzzled how OBS builds against new packages from :Update
when there are no packages listed in the project, and the metadata
shows nothing either.

What's going on behind the scenes to make that work?

And why can't the same magic merge source packages, to make a rollup
release like I want to do?

Webmail for Dialup Users

To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

< Previous Next >