Date: Tue, 10 Oct 2000 21:48:40 -0400 From: Michael Lucas <mwlucas@blackhelicopters.org> To: Mike Meyer <mwm@mired.org> Cc: questions@freebsd.org Subject: Re: library-port matching tool? Message-ID: <20001010214840.A6764@blackhelicopters.org> In-Reply-To: <14819.46272.982612.387928@guru.mired.org>; from mwm@mired.org on Tue, Oct 10, 2000 at 07:30:56PM -0500 References: <127489075@toto.iv> <14819.46272.982612.387928@guru.mired.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Oct 10, 2000 at 07:30:56PM -0500, Mike Meyer wrote: > If you're installing FreeBSD packages, they should notice the > dependency and install the package for you. If they're not doing that, > notify the maintainer of the port from which the package is built. Oh, I don't have this problem with ports. I have this problem with random crap I pull down off the Net. Ports don't give me anything resembling a problem. :) > > Do we have a generalized method of looking up a library to find out > > what port it's in? > Yes, but it sucks: > find /usr/ports -name PLIST | xargs grep <library> Hmmm... does that work if the port isn't installed? -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001010214840.A6764>