Mailinglist Archive: opensuse-buildservice (239 mails)

< Previous Next >
Re: [opensuse-buildservice] Build a whole project with osc
  • From: "Dominique Leuenberger" <Dominique.Leuenberger@xxxxxxxxxxxxx>
  • Date: Wed, 21 May 2008 18:23:37 +0200
  • Message-id: <483476B9.2554.0029.1@xxxxxxxxxxxxx>
On 21.05.2008 at 19:23, Marcus Hüwe <suse-tux@xxxxxx> wrote:
On 2008-05-21 18:05:18 +0200, Michal Marek wrote:
Marcus Hüwe wrote:
On 2008-05-09 20:15:25 +0100, Carlos Goncalves wrote:

As requested by darix, I'm emailing oS-buildservice to ask for a
new osc
feature - capability to build a whole project (eg.
with one single command.
Hmm I think we need one additional api call to retrieve the
buildorder of a
This new call could look like this:


Then we could upload all spec files to the backend, the backend
parses all
specs and calculates the buildorder. Calculating the buildorder
isn't too

Note that the build order might change as you build packages and
dependencies show up. It's probably not too hard but it isn't that
either ;-).
Hmm no. My plan was to send _all_ spec files (or just only
and Provides (we also need to associate this information to a
package)) to the backend.

Imagine the following:
- package "foo" requires "bar-devel"
- package "bar" was added locally ("bar" also provides "bar-devel")

the provides of bar-devel is normally not detected by BS. If you check
in whatever spec file that creates a bar-devel rpm, and another that
Requires: bar-devel, the latter one will stay on Missing dependencies
until bar has built a single time and it will start using this.

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

< Previous Next >
Follow Ups