From owner-freebsd-ports Fri Mar 24 23:35: 8 2000 Delivered-To: freebsd-ports@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id 697AD37B5A0; Fri, 24 Mar 2000 23:35:05 -0800 (PST) (envelope-from will@blackdawn.com) Received: from argon.blackdawn.com ([209.69.196.116]) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id XAA74574; Fri, 24 Mar 2000 23:34:58 -0800 (PST) Received: by argon.blackdawn.com (Postfix, from userid 1000) id 96564193F; Sat, 25 Mar 2000 02:34:49 -0500 (EST) Date: Sat, 25 Mar 2000 02:34:49 -0500 From: Will Andrews To: Ade Lovett Cc: Satoshi - Ports Wraith - Asami , ports@FreeBSD.ORG Subject: Re: cvs commit: ports/x11/kdelibs11 Makefile ports/x11/kdelibs11/pkgDESCR PLIST Message-ID: <20000325023449.E391@argon.blackdawn.com> References: <38DBFB29.20F25F5E@altavista.net> <20000324183603.C391@argon.blackdawn.com> <20000324201752.B6293@lovett.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000324201752.B6293@lovett.com>; from ade@lovett.com on Fri, Mar 24, 2000 at 08:17:52PM -0600 X-Operating-System: FreeBSD 5.0-CURRENT i386 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Mar 24, 2000 at 08:17:52PM -0600, Ade Lovett wrote: > 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. Yes, they are. I just now tested on a variety of KDE ports (including devel/kdevelop). How can I remedy this problem? > 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 *&#!@&^!...." :) Hmm. Sounds like a good idea.. I'll try to find what somebody's .la looks like. Satoshi, can we test this sort of thing on bento? -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message