Hi,
Ok, now happened what I didn't foresee :) I just wanted to
start writing down some CLI specific features when i realized
that in fact we have two CLI executables. The CGI version is
still present and will for a long time, and has its own
command line interface (it's mostly the same, but there are
switches in CGI which aren't in CLI and of course the other
way round).
How we should handle this now?
Write a single CLI chapter, explaining all of the CLI
features and telling people where this differs from the CGI
CLI interface or put up a separate page for the CGI?
Personally I'm for documenting everything, for which I think
keeping CGI command line separate would be a good thing. So
we woukd have a command CLI chapter, documenting fully CGI in
one part and fully CLI in the other. However I'm not that
familiar what's best for docbook organization with such
things.
- Markus
On Mon, May 06, 2002 at 01:04:25PM +0200, Friedhelm Betz wrote :
>
> >> What about Features/Comandline Scripting with the content of
> >> appendices/commandline.xml plus the cli-doku?
>
> > Agreed.
>
> I just moved the commandline.xml from appendices to
> features/commandline (also correcting id and links).
> Docu for cli could go here.
>
>
> Friedhelm
--
Please always Cc to me when replying to me on the lists.
GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc
"I'm not stupid, you know? :)" - Jani Taskinen
