Overview

Request 762591 accepted

3rd party contributions to fastjet library, needed for Rivet >= 3.0


Atri Bhattacharya's avatar
author source maintainer target maintainer

@StefanBruens

Note that rpmlint still grumbles [ 92s] libfastjetcontribfragile.x86_64: W: shlib-policy-missing-lib [ 92s] Your package starts with 'lib' as part of its name, but does not provide any [ 92s] libraries. It must not be called a lib-package then. Give it a more sensible [ 92s] name.



Atri Bhattacharya's avatar
author source maintainer target maintainer

Thanks for the review.

However, I don't know how to correctly package this. The .so file is only needed by someone compiling code against the library, and they will also, therefore, need the headers. Typically in a versioned shared lib, the .so.1.2.3 file goes in the shlib package while the .so symlink to the shared lib goes in the -devel pkg along with all the appropriate headers. In this case, there is no versioned .so.1.2.3 file, so I put everything in the -devel pkg which is the only pkg users and other pkgs will need to compile against. If I put the .so file in a shlib pkg, and the headers in a -devel or -headers pkg, that won't work either, would it? Because anything using the shlib pkg will have to have a separate dependency on the -headers pkg too.


Stefan Brüns's avatar

You put the .so file in the library package, and add a "Requires: lib..." in the devel package (as you would also do when the devel package contained a symlink .so -> .so.1.2.3" ).

The devel-static package also needs a Requires: fastjet-contrib-devel


Atri Bhattacharya's avatar
author source maintainer target maintainer

Makes sense, thanks. Learnt something today 😃

Request History
Atri Bhattacharya's avatar

badshah400 created request

3rd party contributions to fastjet library, needed for Rivet >= 3.0


Atri Bhattacharya's avatar

badshah400 accepted request

openSUSE Build Service is sponsored by