Date: Fri, 05 Aug 2005 08:33:57 -0400 From: "Brandon S. Allbery KF8NH" <allbery@ece.cmu.edu> To: freebsd-ports@freebsd.org Subject: Re: The right way to depend on a package's extra feature Message-ID: <1123245237.36595.9.camel@tirun> In-Reply-To: <20050805073729.GC70957@pcwin002.win.tue.nl> References: <20050805070513.GA60681@sinanica.bg.datamax> <42F310D2.7020200@magnesium.net> <20050805072412.GB70957@pcwin002.win.tue.nl> <42F316A5.9020108@magnesium.net> <20050805073729.GC70957@pcwin002.win.tue.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 2005-08-05 at 09:37 +0200, Stijn Hoop wrote: > On Fri, Aug 05, 2005 at 03:35:01AM -0400, Adam Weinberger wrote: > > Stijn Hoop wrote: > > >I.e. I have both devel/svk and devel/subversion installed. Now, I need > > >devel/subversion because other software depends on it, so I build it > > >with perl bindings by myself. However, devel/svk insists on depending > > >on devel/subversion-perl because it wants the perl bindings -> not > > >good... > > > > But if devel/subversion-perl only contains the perl-enabled stuff that > > devel/subversion doesn't, then devel/svk can just depend on > > devel/subversion-perl, which can in turn depend on devel/subversion. > > Yeah, and right after I wrote this e-mail I realized that there's > something fishy about this, because dependencies are not checked using > port names but using files in the FS; so devel/svk should realize > devel/subversion was built with perl bindings even if I did that by > myself. Actually, I have triggered this one: x11/kde3 depends on devel/svn (via kdesdk3) and then I went to install devel/svk, not realizing that devel/subversion had already been installed without the Perl bindings. **boom** The fix was to force-rebuild devel/svn with the Perl bindings. Another situation I've tripped over (again triggered by kde3) was that if one chooses to build the postgresql client libraries with krb5 support then kde3 doesn't know how to link against them. Arguably this is a bug either in postgresql (not providing a foo-config script that lets programs determine the link libs needed) or whatever part of KDE is linking against it (not checking the link libs) --- but it makes for unexpected link failures. On the other hand, I'm not sure ports should be in the business of dealing with the latter situation. -- brandon s. allbery [linux,solaris,freebsd,perl] allbery@kf8nh.com system administrator [WAY too many hats] allbery@ece.cmu.edu electrical and computer engineering, carnegie mellon univ. KF8NH
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1123245237.36595.9.camel>