Jonas Meurer wrote:
Hey Sune and Barry,
I sent you this mail some days ago, and still didn't get a response. Now
that kde4 is in unstable and lurker ftbfs I'd really fix the issue, but
I don't know how to proceed. A comment from you on the questions below
would be very valuable to me.
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.
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.
- 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. :(
sorry if these questions do sound dump, but i don't have any experience
with library packaging yet :-/
greetings,
jonas
I hope that helps a little.
Thanks,
Barry
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
