Mailinglist Archive: opensuse-packaging (162 mails)

[Cristian Morales Vega <cmorve69@xxxxxxxx>]

2010/2/14 Dave Plater <dplater@xxxxxxxxxxxxxxxx>:
> Hi, the next generation of the package I maintain, blender has a new
> feature called collada which enables 3D import and export similar to
> cad's dxf file format. In order to enable this feature I've had to
> incorporate a package called openCOLLADA into blender and the build of
> the package produces several libraries named :-
> libbuffer.so
> libftoa.so
> libGeneratedSaxParser.so
> libMathMLSolver.so
> libOpenCOLLADABaseUtils.so
> libOpenCOLLADAFramework.so
> libOpenCOLLADASaxFrameworkLoader.so
> libOpenCOLLADAStreamWriter.so
> libUTF.so
> Which following the "Shared_Library_Packaging_Policy" guidlines, I've
> added a 0.0.0 suffix with symbolic links containing plain .so and .so.0.

The "Shared_Library_Packaging_Policy" guidlines say: "SONAME - the
name (query for it using objdump -x libfoo.so.1 | grep SONAME)".
"0.0.0" is really the output you get from objdump or you just used
that because nothing else was available?

> I'm getting several rpmlint warning which would indicate to me that I've
> done something wrong, "W: no-soname" for each lib and

Either these files aren't libraries but plugins (shouldn't be in
/usr/lib and should be packaged in the main blender package or
blender-plugins) or openCOLLADA doesn't follows any versioning scheme.
If the latter, either you worry about maintaining an openSUSE-specific
soname, or it's better to use the static versions of these libraries.

The "Shared_Library_Packaging_Policy" only makes sense if the
libraries maintain sonames that make sense (change every time the
binary compatibility is broken).
-- 
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx