On Sun, 2005-01-23 at 12:02 +1100, Hamish Moffatt wrote: > 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?
With that approach, it's impossible to install several different versions. Or several programs that each depend on a different version of libgeda. The best approach is to just live with it. -- Petri Latvala -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
