Re: ls*, markup and other things

[Alexey M. <mo...@no...>]

=F7 =F0=CE=C4, 06.05.2002, =D7 14:44, Wang Jian =CE=C1=D0=C9=D3=C1=CC:
> AM> bottlenecks and so on). So my question is:
> AM> do we need these commands to have an, hmm, XML-like output? If yes,
> AM> what's the DTD? There're pros (we won't need an unique parser for eac=
h
> AM> command) and cons (the server code needs to be more complex, there wi=
ll
> AM> be greater output size and so on) so final decision should be careful=
ly
> AM> discussed.
> I don't think output of XML-like format is good. The pros doesn't buy
> cons.
Well, I'm also not sure that XML is the way to go. But current format of
lsacl makes me feel terrible. Smth definitely should be changed but
don't know how...

Technically speaking a carefully designed and well-defined XML DTD
doesn't give the server too much additional work. / and //
used now as separators will be changed to number of <> " etc...

Probably there's a better solution though... Any suugestions?

> AM> Now I'm going to commit cvs-create-repository and cvs-group
> AM> commands. Alex, where's the best place to put such things?
Well, we have discussed this in ICQ and decided that perl modules will
go to perl, web-interface will go to web/ or www/
and admin tools - to tools/. Tomorrow morning I'll start to commit
things so everyone is welcome to test and improve.
Particularly improvements will be needed for System::Account module
which helps to create system accounts (via call to
appropriate system tools like useradd). Different systems are supported
via in-module database which describes tools names and switches. I added
support for linux/redhat account tools (useradd and groupadd), support
for other system is still missing but hopefully easy to add.