[bzrweb PATCH] look up repository descriptions in a config file

[Robert Collins]

On Sun, 2005-05-22 at 08:15 -0500, John A Meinel wrote:
> Sean E. Russell wrote:
> > On Saturday 21 May 2005 14:13, John A Meinel wrote:
> > 
> >>But that is quite a bit of overhead for a config file. I would argue for
> >>a standard .ini style, with a mandatory version number, so whatever
> >>changes with time can still be parsed.
> > 
> > 
> > All other comments aside... "standard"?  Standard where?  I've never seen this 
> > before.  What is this ".ini" you're talking about?
> > 
> 
> Well, I can't say that the .ini format is truly standardized, but the
> summary is that sections are denoted with [], and entries are key-value
> pairs delimited with = or :. If an entry is long, it can be continued on
> the next line by using whitespace.
> A # character makes the rest of the line a comment (some also support ;
> as a comment character).
...
> This is still quite a bit to write, and easy to mess up. It is great for
> on over-the-wire protocol, or a long-term-storage protocol, since the
> text is self documenting, and errors are obvious. But for something that
> a human has to edit (possibly often), it is pretty crappy.

I'm completely in favour of .ini files or similar for human edited
configuration, and xml or similar for long term storage. I had some
brief notes on inifiles here http://wiki.gnuarch.org/IniFile when we had
to make similar changes for baz.

Rob


-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20050523/7f946ccf/attachment.pgp