Re: looking for volunteers phpDocumentor, new converterreST
| From: | Tomas V.V.Cox | Date: | Fri, 13 Jun 2003 17:55:41 +0000 |
| Subject: | Re: looking for volunteers phpDocumentor, new converterreST | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev php.pear.doc |
| Request: | Send a blank email to pear-dev+get-17421@lists.php.net to get a copy of this message | ||
----- Original Message -----
From: "Sterling Hughes" <sterling@bumblebury.com>
> # apt-get install python
>
> I don't think its unreasonable to require Perl, Python or PHP, as they
> are pretty major UNIX scripting languages.
>
The full message should be then:
# pear-tool gendoc Package.tgz
The commaind failed to find the proper tools. Please do the following:
1.. Get and install the latest release of Python, available from
http://www.python.org/
Python 2.2 or later 1 is required; Python 2.2.2 or later is recommended.
2.. Use the latest Docutils code. Get the code from CVS or from the
snapshot:
http://docutils.sf.net/docutils-snapshot.tgz
See Releases & Snapshots below for details.
3.. Unpack the tarball and install with the standard
python setup.py install
See Installation below for details
#
If we can live with that, less work to do. The "program dependecy check" is
already supported, so this command could be implemented very easily. We also
need to remember that this feature is focused for developers to easy write
and build doc, only the final formatted doc will be shiped with the package
or published.
My only fear is to choose the correct doc format. This is, not to find an
unsolvable limitation or find that the rubyDocu format is more flexible and
cool in 1 month. That's why I would recommend people to wait for the
http://boogle.com/tmp/2003_meeting_agenda.html
that Phillip pointed out. The
best decision imho is to go together with the php-doc team.
Tomas V.V.Cox