From owner-freebsd-ports  Fri Mar 24 18:17:58 2000
Delivered-To: freebsd-ports@freebsd.org
Received: from viper.lovett.com (hub.lovett.com [216.60.121.161])
	by hub.freebsd.org (Postfix) with ESMTP
	id 2490037B527; Fri, 24 Mar 2000 18:17:54 -0800 (PST)
	(envelope-from ade@lovett.com)
Received: from ade by viper.lovett.com with local (Exim 3.13 #1)
	id 12Yg9A-00029T-00; Fri, 24 Mar 2000 20:17:52 -0600
Date: Fri, 24 Mar 2000 20:17:52 -0600
From: Ade Lovett <ade@lovett.com>
To: Satoshi - Ports Wraith - Asami <asami@FreeBSD.ORG>
Cc: ports@FreeBSD.ORG
Subject: Re: cvs commit: ports/x11/kdelibs11 Makefile ports/x11/kdelibs11/pkgDESCR PLIST
Message-ID: <20000324201752.B6293@lovett.com>
References: <Pine.BSF.4.21.0003241522500.75042-100000@freefall.freebsd.org> <38DBFB29.20F25F5E@altavista.net> <20000324183603.C391@argon.blackdawn.com> <vqcu2hvykk1.fsf@silvia.hip.berkeley.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0.1i
In-Reply-To: <vqcu2hvykk1.fsf@silvia.hip.berkeley.edu>; from asami@FreeBSD.ORG on Fri, Mar 24, 2000 at 04:12:30PM -0800
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

On Fri, Mar 24, 2000 at 04:12:30PM -0800, Satoshi - Ports Wraith - Asami wrote:
> 
> I think this is fine, except for one thing I'm not sure about since
> I'm not a libtool expert -- is there absolutely no way that a piece of
> software would try to read the .la files and try to do something
> sensible with them?

Sadly, there is a way, though I haven't found one that directly
relates to KDE.  I noticed that .la files were being installed by
the lang/librep and x11-toolkits/rep-gtk ports (dependencies of
x11-wm/sawmill) -- removing them by judicious use of USE_LIBTOOL
and a couple of patches rendered the ports unusable in a number
of weird and wonderful ways.

In this particular case (KDE), we'd probably have to look through
the configure scripts and generated Makefiles to see if the .la
files are actually used.

One way to do check this fairly quickly would be to see what
would normally get written into the .la file, and instead use
a simple post-install target to overwrite it with something in
the same format, but with obviously bogus values, eg:

	dlname='libKDEBOGUS.so.666'
	library_names='libKDEBOGUS.so.666 libKDEBOGUS.so'
	old_library='libKDEBOGUS.'
	dependency_libs='-L/KDEBOGUS/lib'
	current=666
	age=0
	revision=0
	installed=yes
	libdir='/KDEBOGUS/lib'

if something actually does use the values from this file, it should
be relatively straightforward to have the package building cluster
pick up on it on the next sweep of the tree.

Comments?  Other than "libtool is a pile of *&#!@&^!...." :)

-aDe

-- 
Ade Lovett, Austin, TX.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message