Mailinglist Archive: opensuse-packaging (158 mails)

< Previous Next >
Re: [opensuse-packaging] Devel packages: Handling factory and older releases
  • From: Johannes Meixner <jsmeix@xxxxxxx>
  • Date: Thu, 16 Sep 2010 12:17:15 +0200 (CEST)
  • Message-id: <alpine.LNX.2.00.1009161207100.11720@xxxxxxxxxxxxxx>


On Sep 16 11:00 Vincent Untz wrote:
Le jeudi 16 septembre 2010, à 10:47 +0200, Andreas Jaeger a écrit :
I've split up a devel package from sane-backends for openSUSE:Factory. I have
added to packages needing the devel library the following:

%if 0%{?suse_version} > 1130
BuildRequires: sane-backends-devel
BuildRequires: sane-backends

This allows the package, e.g. xsane, to build in an original 11.3 environment.

So, now the package works fine - unless sane-backends and the package are in
the same devel project since the split was done unconditionally in sane-
backends. Now the package xsane will not build for older releases since it has
buildrequires on sane-backends but sane-backends in the same devel project has
a separate devel package that would need to be required.

So, how to solve this the best way?

Don't do the %if magic if the package is maintained in the same project
as sane-backends. You really don't need it.

If people take xsane from this project and build it on 11.3 without
taking the dependencies from this same project, then they're doing it
wrong, unfortunately.

Thanks for the info!

Actually it is not xsane but iscan-free which is in the same devel
project "graphics" as sane-backends.

I will fix iscan-free as you suggested.

By the way:

Is it somehow possible to exclude the current devel project
from the repositories where the build service looks for packages
to be installed for the build system?

At least it seems it is not possible to exclude the current devel
project via the web interface because it is not listed in

Kind Regards
Johannes Meixner
SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany
AG Nuernberg, HRB 16746, GF: Markus Rex
< Previous Next >