Re: [opensuse-packaging] How to create baselibs.conf

On 15 May 2012 18:30, Pascal Bleser wrote:

On 2012-05-15 15:22:08 (+0200), Ismail Dönmez wrote:

...

On 05/14/2012 10:45 PM, Pascal Bleser wrote:

...

On 2012-05-14 14:53:23 (+0200), Stephan Kulow [...]

...

I think we're at a point where we should default to create baselibs for all shared library packages by default without this outdated stuff IMO.

...

...

+1, definitely, no reason to have a manual and error prone process for something a script or tool can do easily.

...

So how do we proceed?

I wouldn't even know where to start... in /usr/bin/build ?

Something like home:RedDwarf:test_mkbaselibs:modified. I speak perl as I speak English... Don't get offended if in that patch I say "shit" instead of "sheet". I don't think there is a lot of people used to the full syntax of baselibs.conf (and this should be completed http://en.opensuse.org/openSUSE:Build_Service_baselibs.conf#baselib). And it should be decided what to do when there exists a baselibs.conf file but doesn't say anything about a subpackage: a) Don't create a -32bit file for that subpackage. If the packager wanted such a thing he would have added it explicitly. b) We just changed the *default* to "create a -32bit file". So if the baselibs.conf file doesn't say anything about a subpackage, a -32bit package should be created with the default parameters. Also, this creates "debuginfo-32bit" packages. I guess we want this... but I also guess there is a lot of scripts in the build system with something like "debuginfo$". But in general it seems a quite simple change. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org