Re: Re: the public build of the manual failed
| From: | Paul M Jones | Date: | Sun, 02 May 2004 16:34:55 +0000 |
| Subject: | Re: Re: the public build of the manual failed | ||
| References: | 1 2 3 | Groups: | php.pear.doc |
| Request: | Send a blank email to pear-doc+get-3845@lists.php.net to get a copy of this message | ||
On May 2, 2004, at 11:17 AM, Mehdi Achour wrote:
Lorenzo Alberton wrote:I have to say I agree with Lorenzo; this kind of thing *is* proof of shortcomings (or "cons") in the current system, and highlights one reason why people don't like writing documentation in the PEAR prescribed manner -- high effort, low reward, long feedback loop. Perhaps I am backwards and naive (and I am willing to admit it if true :-) -- but why do we have to "compile and test" documentation pages as if they were part of a Java or C++ program, and then wait a week for a build? It makes no sense to me (and it might be just me :-). -- Paul M. Jones Savant: the simple alternative to Smarty for PHP. http://phpsavant.com/ DB_Table: build RDBMS tables and XHTML forms in one PHP class. http://wiki.ciaweb.net/yawiki/index.php?area=DB_Table Yawiki: your collaborative online documentation system. http://wiki.ciaweb.net/yawiki/index.php?area=YawikiOn Sun, 2 May 2004 10:55:10 -0400, Daniel Convissor wrote:It's not another proof of anything. You shouldn't commit *anything* to the doc module without making test before.Hi Folks: The automatic manual build failed last night. Below are the relevant sections of the build log from http://pear.php.net/manual/en/build.log Can quipo and didou please fix this and then can someone PLEASE manually initiate a rebuild of the manual?sorry, there was an extra opening tag. Some days ago I asked the list to test if my latest commits didn't break anything, but received no reply :-( Sorry again. Well, here's another proof of the difficulties of writing docs without a chance to test them in an online testbed...