[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

relibtoolizing when necessary (was: RFS: knmap -- Kde interface to nmap [uploaded])



Hello *,

On Fri, Jan 13, 2006 at 09:10:32PM +0100, Christoph Haas wrote:
> On Friday 13 January 2006 19:40, Claudio Moratti wrote:
> > On Friday 13 January 2006 15:48, Christoph Haas wrote:
> > > debian/patches: [QUESTION/HINT]
> > >  You are changing a whole lot of the autoconf parts. Does this have
> > >  to do with some transitions going on? Usually just the config.guess
> > >  and config.sub are altered in Debian packages and those are directly
> > >  in the diff.gz (without the need to use dpatch). Just curious.
> >
> > My first sponsor, Florian Ernst, taught me about libtoolization...
> > I relibtoolize every package, if necessary, in order to have a correct
> > and minimal "Depencend" field...
> > this is the reason ;-)
> 
> I thought I understood at least the reason to include diffs for a 
> config.guess and config.sub. But IMHO relibtooling is only needed when 
> certain libraries are in a state of transitions. Could you (or Florian (or 
> anyone)) shed some light on this procedure and the whys? I have never seen 
> this being used as a "common procedure" for packages and would like to 
> learn.

I gave some pointers on relibtoolizing to my sponsees after vorlon
called for improved library handling as mentioned in
<http://lists.debian.org/debian-devel-announce/2005/11/msg00016.html>.
Especially KDE applications seem to be prone to depend on a plethora
of packages they don't really need for functioning due to the admin/
subdir as shipped by kdevelop, so relibtoolizing can save a great deal
here.

For example let's take a look a keurocalc, a package I sponsored for
Claudio. This is the wdiff between before and after proper
relibtoolization:
| Depends: [-kdelibs4c2-] {+kdelibs4c2a+} (>= [-4:3.4.2-1), libart-2.0-2
| (>= 2.3.16), libaudio2,-] {+4:3.4.3-1),+} libc6 (>= 2.3.5-1),
| [-libfam0, libfontconfig1 (>= 2.3.0), libfreetype6 (>= 2.1.5-1),-]
| libgcc1 (>= [-1:4.0.1), libice6 | xlibs (>> 4.1.0), libidn11 (>=
| 0.5.18), libjpeg62, libpng12-0 (>= 1.2.8rel),-] {+1:4.0.2),+}
| libqt3-mt (>= 3:3.3.5), [-libsm6 | xlibs (>> 4.1.0),-] libstdc++6 (>=
| [-4.0.2), libx11-6 | xlibs (>> 4.1.0), libxcursor1 (>> 1.1.2),
| libxext6 | xlibs (>> 4.1.0), libxft2 (>> 2.1.1), libxi6 | xlibs (>>
| 4.1.0), libxinerama1, libxrandr2 | xlibs (>> 4.3.0), libxrender1 (>>
| 1:0.9.0-1), libxt6 | xlibs (>> 4.1.0), zlib1g (>= 1:1.2.1)-]
| {+4.0.2-4)+}
(well, ok, this also includes the g++ transition, but I guess you'll
get the point)

20 Depends were saved, including libfreetype6 which stood at the
beginning of Steve's mail, resulting in a fine and clean
| Depends: kdelibs4c2a (>= 4:3.4.3-1), libc6 (>= 2.3.5-1), libgcc1 (>=
| 1:4.0.2), libqt3-mt (>= 3:3.3.5), libstdc++6 (>= 4.0.2-4)
which actually is all that package really really needs. All the other
Depends were just unnecessarily pulled in.

Of course, maintainers shouldn't relibtoolize just for the sake of it,
but sometimes it's truly worth the effort.

HTH,
Flo

Attachment: signature.asc
Description: Digital signature


Reply to: