Re: How to deal with SONAME which changes very often
Bartosz Fenski aka fEnIo <email@example.com> writes:
> I would like to package some very useful set of utilities.
> It depends on library of the same author.
> Unfortunatelly SONAME of this library changes with every new version.
> And to make this problem more annoying, new releases shows very often
> (about one version per two weeks).
> And now I'm pretty confused with that. Are there any easy ways to
> maintain such libraries/packages? Is it possible to maintain it at all?
> What if I package it with usual way. What if next version of library
> will be released? Should it conflict with previous one? Or leave it
> untouched? Living it leads to situation that Debian will have about 36
> packages after six months. (whole stuff that I would like package is
> divided to three programs/libraries).
> Please give me some hints/suggestions what should be done in such
> situation? Are there any packages with that situation in our archive?
> I'll be very thankful for your answers.
>  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=236090
>  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=241722
Since you are the only one using I would say link it in
static. Problem solved.
But on second thought, seeing that its utilitie_s_, static linking
would waste ram.
But you are still the only one using that library and could combine
the two sources into one package. If the soname changes all the time
both need to be uploaded and recompiled in sync anyway. No point in
making two debs.