Ports, searching - Revision history

Sidetone: /* Updating the search index manually */

2014-12-18T01:12:23Z

Updating the search index manually

Jimbo: Reverted edits by 202.70.201.34 (Talk); changed back to last version by 81.57.238.156

2007-10-04T22:00:18Z

Reverted edits by 202.70.201.34 (Talk); changed back to last version by 81.57.238.156

81.57.238.156: /* Updating the search index manually */

2006-03-09T22:16:22Z

Updating the search index manually

Jimbo: smart usage of grep

2005-09-03T17:01:54Z

smart usage of grep

Jimbo at 19:32, 31 August 2004

2004-08-31T19:32:12Z

Jimbo at 19:31, 31 August 2004

2004-08-31T19:31:22Z

Jimbo at 19:31, 31 August 2004

2004-08-31T19:31:00Z

Dave: /* I know what I want but I don't know what it's called */

2004-08-31T07:04:54Z

I know what I want but I don't know what it's called

Dave at 04:57, 28 August 2004

2004-08-28T04:57:45Z

Dave at 14:32, 26 August 2004

2004-08-26T14:32:19Z

@@ Line 16: / Line 16: @@
 ==Updating the search index manually==
-This step isn't usually necessary, because part of the ports-base collection which you will usually be [[cvsup]]-ing on a regular basis is the INDEX-5 file itself, pregenerated for you by the nice folks who maintain the master tree.  It's also not really recommended where unnecessary, because it can take quite a lot of time to run, especially when using older/slower disks.  But if you suspect your index got corrupted, or if you're running some sort of odd non-standard ports tree (for example you don't maintain local copies of several branches of the tree, etc) you can follow this procedure to generate your own search index.
+This step isn't usually necessary, because part of the ports-base collection which you will usually be [[csup]]-ing on a regular basis is the INDEX-5 file itself, pregenerated for you by the nice folks who maintain the master tree.  It's also not really recommended where unnecessary, because it can take quite a lot of time to run, especially when using older/slower disks.  But if you suspect your index got corrupted, or if you're running some sort of odd non-standard ports tree (for example you don't maintain local copies of several branches of the tree, etc) you can follow this procedure to generate your own search index.
 First, go into /usr/ports as root and make the search index -- making the index can take a while, so go get some coffee or something. Do all of this after you [[Update_the_ports_tree]].)

@@ Line 25: / Line 25: @@
   samizdata# '''make index &'''
 which will make the index so that you can search the ports tree, and run it in the background so that you can do other things. After that finishes, you can search for programs by keyword(s) or by name using your locally-generated index.
 [[Category: Common Tasks]]
 [[Category: Ports and Packages]]

@@ Line 1: / Line 1: @@
 == I know what I want but I don't know what it's called ==
-Fear not: the ports tree is searchable for relevant stuff without having to resort to [[find]], [[grep]] or going through each section in the most mind-numbing way possible.
+Fear not: the ports tree is searchable for relevant stuff without having to resort to using [[find]] or [[grep]] directly on the /usr/ports directory itself - which can be pretty slow - or going through each section in the most mind-numbing way possible.
-  samizdata# '''make search key=browser | more'''
+  samizdata# '''make search key=browser'''
 ... will search for any ports that have anything to do with the key word "browser", or
 ==I know what it's called but I don't know where it is==

@@ Line 8: / Line 8: @@
 ==I know what it's called but I don't know where it is==
   samizdata# '''make search name=lynx | more'''
-will search for any packages by the name you supply, send the output to your screen and [[pipe]] it to the [[more]] command.
+will search for any packages by the name you supply and [[pipe]] the list to the [[more]] command so you can look through it one screenful at a time.
 ==Updating the search index manually==

@@ Line 3: / Line 3: @@
 Fear not: the ports tree is searchable for relevant stuff without having to resort to [[find]], [[grep]] or going through each section in the most mind-numbing way possible.
   samizdata# '''make search key=browser | more'''
 ... will search for any ports that have anything to do with the key word "browser", or

@@ Line 12: / Line 12: @@
   samizdata# '''make search key=browser | more'''
 which will search for any ports that have anything to do with the key word "browser" or
   samizdata# '''make search name=lynx | more'''
 which will search for any packages by the name you supply, send the output to your screen and [[pipe]] it to the [[more]] command.