Hey Barry, On 07/04/2009 Barry deFreese wrote: >>> On Tuesday 17 March 2009 18:29:14 Jonas Meurer wrote: >> i'm willing to maintain it in debian, but some issues remain unclear for >> me, and i'dd highly appreciate your options about them: >> >> - it seems like mimelib doesn't have any real upstream anymore. kdepim >> contains it, and several stanalone tarballs can be found anywhere in >> the web. Barry, how did you find the tarball at ftp.crocodile.org? or >> did you build it on your own? all mimelib versions i can find via >> google (from kde svn, from lurkers sourceforge page, from different >> linux distributions) slightly differ from each other, and i'm really >> unsure about which one is the most recent one. >> for example, i didn't find any mimelib version where the documentation >> files do contain (VCS?) $Revision and $Date entries. Only your version >> from ftp.crocodile.org does have them. >> > Hi Jonas, my apologies, I thought I had responded to your previous > e-mail. I ran into a similar situation. I basically googled around > based on the package and the author. There are mutiple versions flying > around but they are all based on the same lib from the same author. The > ftp.crocodile.org was the most "original" I could find. Then I added > patches based on the modifications that were made in the mimelib stuff > in the kdepim package.
I just compared different versions and I have to say it's really a mess. No version is nearly similar to another one. I don't even understand how you built the mimelib packages at people.debian.org from the tarball at ftp.crocodile.org. The diff between your and the ftp.crocodile.org tarball has more than 10000 lines. 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. I don't expect from you to help me with this, the only thing where you could help is: how exactly did you put the package at people.debian.org together? Is it really based on the tarball from ftp.crocodile.org? >> - when I build mimelib from a seperate source-package, how to coordinate >> this with existing mimelib packages from kdepim sources? sure, I'll >> have to conflict and replace them, but how to name the library package? >> and do I need to introduce a new SONAME? >> another possibility would be to stop building mimelib packages from >> kdepim sources and keep both soname and binary package names the same. >> >> > I'm certainly no expert on library packaging yet but I would name the > library package according to the soname if possible. (I think I did that > in my package). kdepim is going to be removed isn't it? If not, we > have a larger problem as mimelib shouldn't be a seperate package and > shipped in kdepim. If the package name and soname differ from the > kdepim one then yes, adding a Provides and Replaces (and possibly even > Conflicts) would be appropriate. Unfortunately, as you mention I can't > even install or build the kdepim mimelib now so I can't even tell you > what the current soname is. :( 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? I guess most changes from the other tarballs are just minor fixes, but how can I go sure? greetings, jonas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
