[Pkg-kde-extras] Re: KDE packages

[Rizsányi Zsolt]

On Thursday 14 December 2006 14:11, Tom Albers wrote:
> At Thursday 14 December 2006 12:58, you wrote:
> > On Thu, Dec 14, 2006 at 11:39:07AM +0000, Marc 'HE' Brockschmidt wrote:
> > > > * libkexif (0.2.5-2)
> > > > Yes, this is a new upstream version, but it is a bugfix release,
> > > > and it is necessary in order to avoid a lot of problems with
> > > > digikam 0.8.2 (since digikam will be back to this version).
> > >
> > > debian/patches/98_buildprep.diff      |53096
> >
> > +++++++++++++++++++++++++---------
> >
> > > You're kidding, right? Please explain to me why 2/3 of the build
> > > system need to be replaced?
>
> How do I get that diff?

I'm not sure if this is what you are asking, but the buildprep diff is 
generated using the create-buildprep script which is available from the 
pkg-kde svn repository (under svn://svn.debian.org/pkg-kde/scripts) and it 
simply reruns all the makefile magic (with debian/rules buildprep which in 
fact calls the make -f admin/Makefile.common) and then the diff of the 
original source and the one with the changes is put in this diff file.

And to answer the original question: it is necessary so that the make 
system is rebuilt to use the debian tools (libtool). And that is necessary 
so that the library dependencies are reduced to a minimum as it was 
requested on debian-devel-announce 
(http://lists.debian.org/debian-devel-announce/2005/11/msg00016.html)

An alternative to solving this problem would be to invoke the automake 
tools during the normal build of the package, but some do not like this 
solution for various reasons (one being the added overhead on the 
buildd-s).

I did not write this directly to the release team, because I'm not part of 
the pkg-kde-extras team, but you can forward my explanation if you 
consider it satisfactory.

Regards,
Zsolt