Date: Mon, 3 Aug 2009 19:00:35 +0200 From: Tijl Coosemans <tijl@ulyssis.org> To: freebsd-ports@freebsd.org Cc: Garrett Cooper <yanefbsd@gmail.com>, Peter Jeremy <peterjeremy@optushome.com.au> Subject: Re: ports/*/jpeg "Thanks a lot guys" Message-ID: <200908031900.37125.tijl@ulyssis.org> In-Reply-To: <4A76D89B.60803@infracaninophile.co.uk> References: <20090731121249.538ea7e7.jasonh@DataIX.net> <7d6fde3d0908030148h3b5a5934lb0ade13d8b095105@mail.gmail.com> <4A76D89B.60803@infracaninophile.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 03 August 2009 14:31:23 Matthew Seaman wrote: > There was a question about apps that use dlopen() to load libraries, > rather than letting ld.so do the work for them. I don't think that > using ldd(1) will pick up any app that does that, but then again I > don't know if this is a widespread practice, and if it is, whether > there is any simple way to pick out packages that need reinstallation > because of it other than by using manually defined LIB_DEPENDS > settings in port Makefiles. The most common use case for dlopen are plugins and there it's the app that controls the API, not the lib, so an update of the plugin without recompiling the app shouldn't be a problem. Use of dlopen to load normal libraries is rare, but an example is Wine. IMHO it's a bug if such libs aren't listed in LIB_DEPENDS. They are direct dependencies.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200908031900.37125.tijl>