|Edwin Groothuis||Oct 22, 2004 12:45 am|
|Frank Laszlo||Oct 22, 2004 7:36 am|
|Adam Weinberger||Oct 22, 2004 7:36 am|
|Robin Schoonover||Oct 22, 2004 9:01 am|
|Robert Huff||Oct 22, 2004 9:16 am|
|Benjamin Lutz||Oct 22, 2004 9:23 am|
|Robert Huff||Oct 22, 2004 9:24 am|
|Mark Linimon||Oct 22, 2004 9:32 am|
|Mike Edenfield||Oct 22, 2004 9:33 am|
|Oliver Lehmann||Oct 22, 2004 9:46 am|
|Robert Huff||Oct 22, 2004 10:41 am|
|Lowell Gilbert||Oct 22, 2004 1:07 pm|
|Lowell Gilbert||Oct 22, 2004 1:08 pm|
|Paul Chvostek||Oct 22, 2004 1:14 pm|
|Robin Schoonover||Oct 22, 2004 3:52 pm|
|Christopher Nehren||Oct 22, 2004 3:54 pm|
|Paul Chvostek||Oct 22, 2004 5:17 pm|
|Parv||Oct 22, 2004 6:55 pm|
|Jim Trigg||Oct 22, 2004 8:26 pm|
|Michael Nottebrock||Oct 24, 2004 8:24 am|
|Jose M Rodriguez||Oct 24, 2004 8:47 am|
|Jie Gao||Oct 26, 2004 12:40 pm|
|Tillman Hodgson||Oct 26, 2004 12:47 pm|
|Matt Douhan||Oct 26, 2004 12:54 pm|
|Tillman Hodgson||Oct 26, 2004 1:01 pm|
|Jie Gao||Oct 26, 2004 4:19 pm|
|Michael Nottebrock||Oct 26, 2004 5:59 pm|
|Michael Nottebrock||Oct 26, 2004 6:01 pm|
|Benjamin Lutz||Oct 26, 2004 7:13 pm|
|Robert Huff||Oct 26, 2004 7:49 pm|
|Tillman Hodgson||Oct 26, 2004 8:12 pm|
|Mark Linimon||Oct 26, 2004 8:35 pm|
|Mark Linimon||Oct 26, 2004 8:41 pm|
|Tillman Hodgson||Oct 26, 2004 9:03 pm|
|Matthew Seaman||Oct 27, 2004 1:17 am|
|Frank J. Laszlo||Oct 27, 2004 4:02 am|
|Tillman Hodgson||Oct 27, 2004 7:07 am|
|Roman Neuhauser||Nov 9, 2004 5:11 pm|
|Radek Kozlowski||Nov 9, 2004 5:31 pm|
|Roman Neuhauser||Nov 10, 2004 4:59 pm|
|Subject:||ports/www is too full|
|From:||Tillman Hodgson (till...@seekingfire.com)|
|Date:||Oct 27, 2004 7:07:16 am|
On Wed, Oct 27, 2004 at 09:17:41AM +0100, Matthew Seaman wrote:
About the only way I can see for doing this task effectively would be a google-like keyword search over the contents of the pkg-descr files. The pkg-descr files generally contain a pretty good summary of what the port actually contains -- much better than just relying on port names. Hmmmm... it should be possible to hook up htDig indexing the README.html files.
It would be better, yes, but it would still be playing "hunt the keyword in the stack of 12000 pkg-descrs". If you picked a good keyword you get 200 hits and still have to browse through them. If you pick a bad keyword, you get no hits.
Perhaps if pkg-descr had a KEYWORDS: line and it's use was considered mandatory ... but what are the chances that every port maintainers idea of a keyword is the same as mine?
I think meta-information like fine-grained categories are different than searching.
Although did you just try typing in 'apache modules' into the search facility right on the http://www.freebsd.org/ports/ page? You can even tell it to just search the package descriptions.
Oh, I agree that there are tools out there that do very cool things with the ports tree. I'm a regular spelunker (love that word) at freshports.org. That's not exactly part of the FreeBSD tool set on a non-networked machine though, so I don't think it's _directly_ relevant to this discussion.
I'm not even advocating the use of finely-grained categories. I'm just pointing out that searching is not the same as browsing :-). I wouldn't use Google to select the right chapter of the Handbook to read--I'd use the table of contents. Searching is useful, and it's very important and thus worth spending time getting right, but it's a different tool for a different (albeit related) task.
Here's a better example:
Let's say that rather than being the maintainer of the net/latd port, I'm some random user who wants the `llogin` program. So I `cd /usr/ports && make search key=llogin`. But there's no hits.
There's 989 ports in the net/ category. Searching failed. Browsing that directory for the port I want is very difficult. But if there was, say, a dozen sub-categories my task becomes manageable. Maybe in the net/other-protocols (or whatever) category there's only a score of ports. Maybe the name "latd" then rings a bell.
Granted, the ability to search pkg-plist would solve this particular issue. It's easy to find examples where that won't work: if I just want to see what neat kinds of network protocols that FreeBSD has supported in it's ports tree, for example.
-- Page 41: Two of the most important Unix traditions are to share and to help people. - Harley Hahn, _The Unix Companion_