On Mon, Sep 19, 2011 at 03:50:29PM +0200, Jan Engelhardt wrote:
On Monday 2011-09-19 14:58, Vincent Untz wrote:
Hi Jan,
Le lundi 19 septembre 2011, à 02:44 +0200, Jan Engelhardt a écrit :
automated: - removal of '# norootforbuild' - removal of 'AutoReqProv: on' since this is default anyway manual: - removal of Authors list, no longer desired in factory - removal of %clean section, no longer required - removal of rm -Rf %buildroot in %install when spotted, [1] - changing %{?%jobs:-j%jobs} to %_smp_mflags, [1] - adding %{?_smp_mflags} whereever there is none, or - tagging places more explicitly where parallel build does not work by utilizing the grepable string "-j1" plus a comment if none exists - replacing CFLAGS="$RPM_OPT_FLAGS" ./configure --bindir=%_bindir --infodir=%_infodir ... (and similar) by %configure [shorter] - shlib policy where it seems quick - killing old %changelog (because it's in .changes already)
One other change I'm seeing in some sr is the addition of devel subpackages to baselibs.conf. I don't think it's needed in most cases. Or is there some rationale for it?
Often enough I have found myself in a position where I would like to test $PROGRAM in a non-default compilation mode, and that requires that all libraries also exist.
(Point in case, I was asked to try prboom-plus in 32-bit mode, which required adding -devel to baselibs for at least the entire SDL stack. And some developers prefer a quick local compile rather than having to upload a new tarball into OBS and wait for the result -- also the latter has licensing constraints.)
I am therefore of the opinion that -devel in [certain] baselibs that I am interested in is alright.
This is for instance useful for people building Wine on 64bit, where you usually want to build the 32bit version and not just the 64bit version. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org