Mailinglist Archive: opensuse-buildservice (332 mails)

< Previous Next >
Re: [opensuse-buildservice] project configs and macros
  • From: Jon Nelson <jnelson-suse@xxxxxxxxxxx>
  • Date: Sun, 11 Jul 2010 14:42:44 -0500
  • Message-id: <AANLkTikanVVsuSaFgVgEqY3CzOC6O18GMsazw4czb_IH@xxxxxxxxxxxxxx>
On Sun, Jul 11, 2010 at 2:29 PM, Jon Nelson <jnelson-suse@xxxxxxxxxxx> wrote:
On Sun, Jul 11, 2010 at 10:23 AM, Robert Xu <robxu9@xxxxxxxxx> wrote:
On Jul 11, 2010, at 11:10, Jon Nelson <jnelson-suse@xxxxxxxxxxx> wrote:

On Sun, Jul 11, 2010 at 3:10 AM, Jan Engelhardt <jengelh@xxxxxxxxxx>
On Sunday 2010-07-11 01:09, Jon Nelson wrote:


%define fooversion 25
fooversion 25

Because it's supposed to be

%fooversion 25

and that only.

OK. I was patterning things after what I found here:

osc meta prjconf CentOS:CentOS-5

although I got it partly wrong (I had the %define line after Macros:).

The output from that command has the following (pasted exactly, minus
the '=' lines):


Substitute: popt-devel popt

%define centos_version 501

%opensuse_bs 1
%centos_version 501
%_vendor redhat


According to the docs, the "%define centos_version 501" line is usable
*only* in the project config, and the macros defined after the
"Macros:" line are usable in spec files as though they appeared in

Is that correct?

OK, but what about my other questions. Are they stacked or appended

Let's say I have FooDistro-1.0 and FooDistro-2.0 (these are for
sources only, no packages get built).
Let's say I have stuff:apple and stuff:banana.  stuff:apple has build
repos for both FooDistro versions.
stuff:banana only makes use of stuff:apple.

In both FooDistro project configs, following "Macros:", I have:

%foodistro_version 10
%define foodistro_version 10

I've given it a try and it does not appear to be stacking the way I
expect, or I'm doing it wrong.

I have the following projects:

A B C and D.

A and B are different versions of the same base distro.
C has A and B as build repositories.
D has C has a build repository.

A and B have project configs that look like this:

A has this:

%define foo_version 10

and that line does not follow the Macros: line.

B has this:

%define foo_version 20

and that line does not follow the Macros: line.

C has this as it's *only* project config:

%if 0%{?foo_version} == 10
Substitute: packageA packageB

%if 0%{?foo_version} == 20
Substitute: packageB packageA

However, packages built in project C for repo A (which should have
foo_version 10) are using packageB. If the Substitute directive was
being followed, that should not be.

How do I debug this? It feels like a black box and I've tried lots of
permutations without luck.

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

< Previous Next >