[opensuse-buildservice] about prj name "SLE_11" vs "SLE_11_SP1" vs "SLE_11_SP2"
Hi @all can we please stop with this "SLE_11_SP?" naming and stick on "SLE_11" And the webui should not provide 3 prjs for SLES 11, just one "SLE_11" configure with "SUSE:SLE-11:SP1" (at a miniumum) This naming changes will break "_aggregate" packages. why at a miniumum SP1 ? - GA is not suppoerted anymore - any build on SP1 should run on SP2 without any problems. and what to do when SP3 is out ? then use at a minimum SP2. -- Christian ---------------------------------------------------- - Please do not 'CC' me on list mails. Just reply to the list :) ---------------------------------------------------- Der ultimative shop für Sportbekleidung und Zubehör http://www.sc24.de ---------------------------------------------------- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christian [18.04.2012 13:47]:
Hi @all
can we please stop with this "SLE_11_SP?" naming and stick on "SLE_11" And the webui should not provide 3 prjs for SLES 11, just one "SLE_11" configure with "SUSE:SLE-11:SP1" (at a miniumum) This naming changes will break "_aggregate" packages.
why at a miniumum SP1 ? - GA is not suppoerted anymore - any build on SP1 should run on SP2 without any problems.
and what to do when SP3 is out ? then use at a minimum SP2.
What about packages that produce kernel modules? SLE 11 SP2 includes Kernel 3.0.x. A module for this kernel can't be built with SP1 kernels, or am I wrong? Werner - -- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+OyfsACgkQk33Krq8b42MHsQCeKu6izubbPqeXvHn5A1XLSpjQ UGIAn2DTx2pENklowbsWra7vWd/AS3ZS =fPER -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 2012-04-18 16:04:43 (+0200), Werner Flamme <werner.flamme@ufz.de> wrote:
can we please stop with this "SLE_11_SP?" naming and stick on "SLE_11" And the webui should not provide 3 prjs for SLES 11, just one "SLE_11" configure with "SUSE:SLE-11:SP1" (at a miniumum) This naming changes will break "_aggregate" packages.
why at a miniumum SP1 ? - GA is not suppoerted anymore - any build on SP1 should run on SP2 without any problems.
and what to do when SP3 is out ? then use at a minimum SP2.
What about packages that produce kernel modules? SLE 11 SP2 includes Kernel 3.0.x. A module for this kernel can't be built with SP1 kernels, or am I wrong?
You're right. But arguably, there are only very, very few projects that do build kernels or kernel modules. The current scheme is "polluting" it for everything else :\ Not sure how well things work (or not) when one changes "SLE_11" from "SUSE:SLE-11:SP1" to "SUSE:SLE-11:SP2": causes full rebuild? Easy to monitor that rebuild and its failures? cheers -- -o) Pascal Bleser /\\ http://opensuse.org -- we haz green _\_v http://fosdem.org -- we haz conf
On 04/18/2012 01:47 PM, Christian wrote:
Hi @all
can we please stop with this "SLE_11_SP?" naming and stick on "SLE_11" And the webui should not provide 3 prjs for SLES 11, just one "SLE_11" configure with "SUSE:SLE-11:SP1" (at a miniumum) This naming changes will break "_aggregate" packages.
why at a miniumum SP1 ? - GA is not suppoerted anymore - any build on SP1 should run on SP2 without any problems.
and what to do when SP3 is out ? then use at a minimum SP2.
Without repeating the points I made several weeks ago (and together with darix again today), just don't add SP2 repo paths to your "SLE_11" repo but add the default SLE_11_SP1 and SLE_11_SP2 repos instead. Outcome: No aggregates broken, no repos to be renamed (and pushed to mirrors) which means no user's zypper repository configuration broken and no binaries broken for SLE_11_SP1 users having installed SLE_11_SP2 libs or binaries from your 'SLE_11' repo. Besides that, mls and me just checked it, there aren't many OBS projects that have a 'SLE_11' repository configured like you propose. Even devel:libraries:c_c++ has the correct setup by now ;-) -- Viele Grüße, Sascha Peilicke
Am Mittwoch, 18. April 2012, 13:47:24 schrieb Christian:
Hi @all
can we please stop with this "SLE_11_SP?" naming and stick on "SLE_11" And the webui should not provide 3 prjs for SLES 11, just one "SLE_11" configure with "SUSE:SLE-11:SP1" (at a miniumum) This naming changes will break "_aggregate" packages.
I do not buy the agrument that it breaks aggregates. When using aggregates you already need to know VERY exactly what you are doing, because it can get broken also very easily in other ways (eg. via adding a new dependency or via package splits).
why at a miniumum SP1 ? - GA is not suppoerted anymore - any build on SP1 should run on SP2 without any problems.
You can still build also against SP0 (SUSE:SLE-11) project and keep SLE_11 name. IMHO only very few projects do need to use newer versions.
and what to do when SP3 is out ? then use at a minimum SP2.
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 2012-04-19 10:30:22 (+0200), Adrian Schröter <adrian@suse.de> wrote:
Am Mittwoch, 18. April 2012, 13:47:24 schrieb Christian: [...]
why at a miniumum SP1 ? - GA is not suppoerted anymore - any build on SP1 should run on SP2 without any problems.
You can still build also against SP0 (SUSE:SLE-11) project and keep SLE_11 name. IMHO only very few projects do need to use newer versions.
Well, there is forward compatibility too: SP2 ships newer versions of some libraries, e.g. gtk2 or qt4, if I'm not mistaken. And suddenly there is a boatload of packages that we _can_ build for SP2 which we couldn't build for SP0 (because those libs were way old on SP0 or even SP1). cheers -- -o) Pascal Bleser /\\ http://opensuse.org -- we haz green _\_v http://fosdem.org -- we haz conf
participants (5)
-
Adrian Schröter -
Christian -
Pascal Bleser -
Sascha Peilicke -
Werner Flamme