On Sunday 19 April 2009 04:48:49 Jonas Meurer wrote: > I now have five different versions of mimelib available: > - your debian package from people.debian.org/~bdefreese > - the kdepim3 source package from debian/squeeze > - the source tarball from ftp.crocodile.org > - the source tarball from sourceforge.net/projects/lurker > - the svn snaphost from svn.kde.org > > I could just pick up one, finish the packaging, and upload it. But to be > honest, I would like to first sort out why all these versions do have tens > of thousands of changes each.
Mimelib was abandoned by its maintainer around 10 years ago, and people have had different needs. No effort has been made to try unify these. > kdepim3 is gone from debian/unstable now, so it shouldn't be a problem > to upload source package mimelib with binary packages libmimelib1 and > libmimelib1-dev any more. > > The libmimelib1c2a package has libmimelib.so.1 as soname. If I want to > keep the soname, I'll have to ensure abi compatibility. How can I check > that in case that I use a different source than kdepim3? If you want to keep same packagename (and SONAME), you need to check thoroughly that is having the same ABI. You can among other check with objdump wether it is the same symbols that are exported. You can also choose to name it differently, and then you just have to make sure that lurker works. /Sune -- I cannot telnet to the URL to the microprocessor, how does it work? You either can never save on a forward, or cannot install a SIMM over the command prompt in order to log on a 4-bit SCSI line. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
