https://bugzilla.novell.com/show_bug.cgi?id=770243
https://bugzilla.novell.com/show_bug.cgi?id=770243#c2
Johannes Meixner changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |ASSIGNED
InfoProvider|jsmeix@suse.com |
--- Comment #2 from Johannes Meixner 2012-07-10 08:28:43 UTC ---
If it is impossible to distinguish SLE service packs
during build, it would mean that the build environment
must be exactly the same for different SLE service packs.
In general this is true (we try to be backward comatible
for different SLE service packs) but this is not true
in any case.
It is probably true for those package versions which we have
in SLE_GA. But for the newest package versions there can be
differences how to build them well (i.e. without the need
for awkward obscure hacks) for different SLE service packs.
In OBS development projects I build the newest package versions
for various products, ideally for SLE_10, SLE_11, SLE_11_SP1,
SLE_11_SP2, openSUSE_11.4, openSUSE_12.1, openSUSE_Factory,
and openSUSE_Tumbleweed.
Therefore I need to know the exact build environment
in the spec file to be able to build it even in special
cases for all those products via one same spec file,
something like
---------------------------------------------------------------
%if 0%{?sles_version} == 11
something_for_all_SLE11
%if 0%{?sles_sp_version} == 110
something_special_for_SLE11_GA
%endif
%if 0%{?sles_sp_version} == 111
something_special_for_SLE11_SP1
%endif
%if 0%{?sles_sp_version} == 112
something_special_for_SLE11_SP2
%endif
%endif
---------------------------------------------------------------
so that it is clear in particular for external contributors
who work with our spec files what happens therein.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
