geda library packaging
Following on from the recent discussions about library packaging, I
could use some advice from the experts on the best way to handle
packaging of libgeda.
The situation is as follows. gEDA consists of a library package and a
bunch of program packages. They come from upstream in different
tarballs, but they are all released together. I maintain all of the
packages that use libgeda and I don't anticipate that changing soon.
Upstream increments the soname for incompatible changes to the library.
I've been reflecting that in the package name (libgedaXX) which means
we've had libgeda2, 3, 5, ... 18, 19, 20. Almost every new version
requires a new package, with NEW processing by ftp-masters etc.
That doesn't seem ideal to me.
So I suspect it's better if the binary package was just called libgeda,
and that the program packages depended on a specific version. However it
needs to be the exact upstream version without being a particular debian
revision.
Any suggestions for the best approach?
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
Reply to: