> I like install/ and install/configure makes sense > but ini, imho, should be different. How > about making yet another root directory, /ini/. > > Many people look at 'ini' information and never > install PHP. Whether it be used for ini_set, > .htaccess or php.ini ... it's not really an install.
configure and ini parts are tied to each other in many respects. For example configure options determine what ini options are useable. Think of install+configure+ini as a group of "setup" related tasks. These are connected to each other heavily. All the other parts are related to "usage", these three ones are related to "setup". Well, actually Zend parts are related to "develop", but that's another question... > > If we can make up a table "previous ID", "new ID", > > process.php can do any changes in links to pages, > > so as long as ID changes are consequent, we can go > > on with that too... > > It'd be nice if we could get a list of the most > popular terms sent to php.net search box, and > have those point directly to useful places in > the manual in a similar fashion. But, that's a > different topic and bag of worms :) Well, I am just implementing a new shortcut function for php.net pages, to allow people to access pages without php extensions, like http://www.php.net/docs http://www.php.net/downloads These types of shortcuts makes php mailing list replies easier to type, like "download lates binaries from "php.net/downloads". I also thought about adding a common list of shortcut names (like "ini", "windows", "linux", "macos"). So feel free to suggest such shortcuts. Goba
