Source: libfilezilla Dear maintainer,
I see that you keep regularly uploading new versions of this library and
each has a different SONAME, so that you keep renaming the binary
package.
Now, that package contains both the library and some supporting files
(for i18n) that share a common path between different versions of the
library, forcing you to add Conflicts against the older version.
That is kind of annoying to me, who is used to run `apt upgrade` which
doesn't remove packages. I've come in the past years to rely on just
that for most of my system upgrade needs, as dist-upgrade became less
and less needed, opposed to what used to be years ago.
I see several ways so that libfilezilla could also allow for smooth
transitions between its versions*, so could you please consider one of
them? :)
Besides, I don't think it's a problem for this specific library since it
only has one user and you control it, but it would make the testing
migration potentially easier as well.
Thanks for considering!
* not limited to:
+ move the i18n files into some soname-named path
+ move the i18n files into a -common binary that is then used by
multiple versions of the library
+ embed the data into the library itself
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
