On Mon, Jan 3, 2022 at 7:08 PM Scott Talbert <swt(a)techie.net>
wrote:
>
> On Mon, 3 Jan 2022, Ian McInerney wrote:
>
> > Spurred off of the recent lxqt thread in devel
> >
(
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
> > ) that bumped the soname for another library in the stack without
> > announcing that one, I looked in the packaging guidelines to see if
> > there was anything about how to represent the soname version in the
> > spec and didn't see anything.
> >
> > I know I have seen some mention on the devel list about using a
> > global
> > define to set the so version, and then using that in the %files
> > section
> > instead of a glob on the shared library so that an so version bump
> > is
> > caught at build time and errors it without packager intervention,
> > but
> > that doesn't appear to be listed in the packaging guidelines at
> > all.
> > What are people's thoughts on adding a section about handling so
> > versions alongside the soname section? It say to use the global
> > define/no glob method in the spec (although I haven't decided if I
> > think
> > it should be a SHOULD or a MUST criteria). I feel that could help
> > reduce
> > these unannounced breakages that seem to crop up and that are
> > annoying
> > to scramble to fix afterwards.
> >
> > Thoughts? Or did I overlook a place in the packaging guidelines
> > that
> > already discusses this?
>
> There's this section[1] that states that you SHOULD NOT use a glob
> for
> %files, but it doesn't talk about using a macro.
>
> [1]
>
https://docs.fedoraproject.org/en-US/packaging-guidelines/#_listing_share...
>
Something I've done in openSUSE and Mageia that might be worth doing
in Fedora is a namespaced glob, where the somajor is specified and the
sublevels are globbed.
You can see an example of this with my fdk-aac-free package in
openSUSE here:
https://code.opensuse.org/package/fdk-aac-free/blob/4d35a883c89e7569349fc...
Admittedly, it's a lot easier for me to do it this way in openSUSE and
Mageia rather than Fedora since I also need to name the library
packages with the somajor in them...
--
Sérgio M. B.