Date: 11 Mar 2002 00:58:59 +0200 From: Maxim Sobolev <sobomax@FreeBSD.org> To: Garrett Rooney <rooneg@electricjellyfish.net> Cc: Jimmy Olgeni <olgeni@FreeBSD.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/www/neon pkg-plist ports/www/neon/files patch-ltmain.sh Message-ID: <1015800125.527.61.camel@notebook> In-Reply-To: <20020310222434.GA4251@electricjellyfish.net> References: <200203102057.g2AKvhx56286@freefall.freebsd.org> <1015798632.527.40.camel@notebook> <20020310222434.GA4251@electricjellyfish.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-164oKm9QUbrxtTkxsHGv Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2002-03-11 at 00:24, Garrett Rooney wrote: > On Mon, Mar 11, 2002 at 12:17:35AM +0200, Maxim Sobolev wrote: > > On Sun, 2002-03-10 at 22:57, Jimmy Olgeni wrote: > > > olgeni 2002/03/10 12:57:43 PST > > >=20 > > > Modified files: > > > www/neon pkg-plist=20 > > > www/neon/files patch-ltmain.sh=20 > > > Log: > > > Install libneon.la, which is needed by the devel/subversion port. > >=20 > > Just wonder why does it need it? Looks like a bug to me. >=20 > The subversion build system is set up so that you can build with neon > either in the subversion tree or out of it. As a result, it tries to > use the libneon.la file, since neon normally installs it. I could > hack around it, but it doesn't make much sense to me to patch one port > (neon), changing what it installs, thus requiring us to patch still > more ports (subversion, plus whatever else might depend on neon > installing that file). To me anyway, it seems fairly reasonable for > someone to assume the file will be there, since neon installs it by > default anyway. This isn't entirely correct assertion, because .la file installed by libtool, whose behaviour in this area is system-specific. Therefore, in fact broken is subversion autoconfiguration system, because it checks for the presence of neon library using wrong way (just for the moment imagine that there is another fully compatible neon library, which doesn't use libtool and therefore doesn't install .la file). The right way is to test whether it's possible to link test application with -lneon, not check that there is a libneon.la file. Most of the ports in our tree do the right thing about this OOB, all those that don't should be fixed and the problem reported to vendor. > Why not just avoid the mess entirely and install the file? Because that would be a workaround. -Maxim --=-164oKm9QUbrxtTkxsHGv Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQA8i+E9oNu5t4iCBa8RAjDaAJ0dCgJi63HUlXvkpBsc0DDISLUpewCfctmh KpkeYGQvK8822DUYdzWL/f8= =eiJ4 -----END PGP SIGNATURE----- --=-164oKm9QUbrxtTkxsHGv-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1015800125.527.61.camel>