Mailinglist Archive: opensuse-packaging (118 mails)

< Previous Next >
Re: [opensuse-packaging] suse_version handling troubles/solutions


On Thu, Jun 11, Tomáš Chvátal wrote:

Introduce extra macro, ie %opensuse_version YYYYMMDD which would be based on
the snapshots and always bumped, so we can seriously finegrain what to enable.

This has problem if we backport back the features back to SLE so suddenly
are supposed to be covered just by %suse_version thing.

Or we would need to mesh in that anything %suse_version 12 %opensuse_version
ANYTHING is older than %suse_version 12.1...

Don't really understand what you want to reach here.

Redo how we think about optional features and why we use the suse_version.

Instead of
%if suse_version > 1140
BuildRequires: bla
We could devise in rpm like TryBuildRequires which would pull in packages if
they are around and otherwise provide some packagename = 0 for further
depending conditions.

This would become a nightmare, since the package feature set would depend
on which other RPMs are by design or luck in a repo or not.
Means in one home project it works, in another it does not work. Or
it works in the devel project where the package 'bla' is missing, and
stops working in Tumbleweed, where the package 'bla' is available.


Thorsten Kukuk, Senior Architect SLES & Common Code Base
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nuernberg, Germany
GF: Felix Imendörffer, Jane Smithard, Dilip Upmanyu, Graham Norton, HRB 21284
(AG Nürnberg)
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups