Date: Thu, 20 Oct 2005 20:20:31 -0400 From: Parv <parv@pair.com> To: Benjamin Lutz <benlutz@datacomm.ch> Cc: nocturnal <nocturnal@swehack.se>, freebsd-ports@freebsd.org Subject: Re: Flaws in the ports system? Message-ID: <20051021002031.GA12167@holestein.holy.cow> In-Reply-To: <435825F8.4020305@datacomm.ch> References: <4357D830.7060506@swehack.se> <435825F8.4020305@datacomm.ch>
next in thread | previous in thread | raw e-mail | index | archive | help
in message <435825F8.4020305@datacomm.ch>, wrote Benjamin Lutz thusly... > > - Searching. Personally, I strongly dislike make search because its > way too verbose. Search results easily fill several screenfuls, > and grepping it is not trivial. I've worked around this one by > creating a tool that writes grep-able sub-indexes to disk in a > more concise format, the tool's available here: > http://www.maxlor.com/freebsd-scripts.shtml It seems anybody who does not like "make search" and is able to generate an alternative, does. I did. And so did[0] Matthew Seaman by having sysutils/p5-FreeBSD-Portindex in the ports system. From the port's description file ... cache-init, cache-update, find-updated and portindex are a set of perl scripts built around the common core of the FreeBSD::Portindex modules. Their use is to generate and maintain the ports INDEX or INDEX-5 files speedily and efficiently. Ultimately they work in a very similar way to the standard make index command, except that the FreeBSD::Portindex tools keep a cache of the make describe output from each port, and can update that cached data incrementally as the ports tree itself is updated. WWW: http://www.infracaninophile.co.uk/portindex/ [0] I am not speaking on behalf of Matthew S, but making one particular point. - Parv --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051021002031.GA12167>