Hello, On 17/03/2009 Sune Vuorela wrote: > On Tuesday 17 March 2009 18:29:14 Jonas Meurer wrote: > > on final issue remains: > > I saw that the package build-depends on kdelibs4, which is from kde3. > > But I thought that the bugreport was filed by Sune to get rid of kde3 in > > the long term. > > It is still unclear wether we can get rid of the kde3 libraries for squeeze. > I > hope it is, but I don't think it is realistic. > > But mimelib should be enough self-containing to not require any parts of KDE > - > and mimelib don't expose any parts of kde abi to the outside. It should be > doable, it is just a matter of doing it. > > > Is this build dependency required at all? An if it is, how do you intend > > to workaround it once kde3 will be removed from debian/unstable?
I managed to get rid of the kdelibs build-dependency by simply replacing #else # include <kde/kdemacros.h> # define DW_EXPORT KDE_EXPORT #endif with #else # define DW_EXPORT #endif in mimelib/config.h. So indeed a mimelib source package which is independent from any kde libraries shouldn't be a problem. 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. - 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. sorry if these questions do sound dump, but i don't have any experience with library packaging yet :-/ greetings, jonas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
