Matthew Peters wrote: > we just tried the experiment of naively moving the two directories > sdodasrel and sdo_das_xml inside the sdo directory and running make > html. That didn't work. I guess the build process won't automatically > look for reference.xml in subdirectories.
If I understand it well, if someone installs SDO, he automatically gets sdo_das_xml. So my idea was that it should be documented together, in one section and one function list. But it can be discussed further, others might have other opinion. BTW, in sdo_das_xml/reference.xml is: > There are additional installations steps required. Is this true and additional installations steps will be documented later or "no" is simply missing? > We want to keep the structure we have where the documentation for the > two DASs look like the documentation for a regular extension (sections > for installation, functions, etc.) but have everything neatly in the sdo > directory. Do you know how we achieve this? If you want it to leave it separate and others don't mind, leave it. I think "one chapter - one directory" is good rule and there's no need to move one directory to the other. > 1. I don't understand the build process well enough to know why the sdo > section is appearing on http://docs.php.net/ but the two DAS sections > aren't. Is there a manual step needed? And when do things get promoted > to php.net? docs.php.net runs on Livedocs and ./configure is needed to get new sections AFAIK. I'm not sure if it is done periodically or manually. It will get promoted to php.net with the next manual built done by Derick from time to time (sometimes weekly, sometimes quarterly :-)). Jakub Vrana
