Date: Wed, 23 Mar 2011 11:38:18 -0700 From: Doug Barton <dougb@FreeBSD.org> To: Olivier Smedts <olivier@gid0.org> Cc: freebsd-ports@freebsd.org, Peter Jeffery <peterj@mister-j.dyndns.org> Subject: Re: [HEADS UP] Ports Infrastructure Changes Message-ID: <4D8A3E1A.7040001@FreeBSD.org> In-Reply-To: <AANLkTikNC0ET6CcOvHHJnvZwxaLpxpyVKBHt77jRo_Xm@mail.gmail.com> References: <alpine.BSF.2.00.1103192316110.84574@dee.signature.nl> <AANLkTim5Lf31sJH634sb976xDsekg53jQmvenYcuR9dq@mail.gmail.com> <op.vsslnf05oxde33@pete01.gateway.2wire.net> <4D8A2A79.4010908@FreeBSD.org> <AANLkTikNC0ET6CcOvHHJnvZwxaLpxpyVKBHt77jRo_Xm@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/23/2011 11:34, Olivier Smedts wrote: > 2011/3/23 Doug Barton<dougb@freebsd.org>: >> On 03/23/2011 03:48, Peter Jeffery wrote: >>> >>> If I was looking for the Opera port, I'd look in www-clients and if >>> it wasn't in there then the next thing that I would be doing is hand >>> searching the INDEX file >> >> cd /usr/ports/&& make search name=opera > > Or > find /usr/ports -maxdepth 2 -name opera > Slower than make search but faster than building an INDEX file before > make search ! Who said anything about building an INDEX? :) If you use portsnap to update your ports tree it comes along for free. If not, then 'make fetchindex' will do the trick for you. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D8A3E1A.7040001>