You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Daniel Stenberg <da...@haxx.se> on 2000/09/14 07:16:04 UTC

config file q

quote from "notes/svn-config-files":

  Let's rethink this, and create a system which allows "nesty" syntax,
  something like scheme.

  The main point is still to define sections/keys/vals.

I'm not fully aware about for what the config files are gonna be used and for
what contents, but the wording of this remark made me think of some software
I wrote once. A config file system that is very hierarchical and I was
thinking something like that could be this 'which allows "nesty" syntax'.

It supports a config file that looks like:

foo{
  name{bar}
  version{2}
}
bar{
  name{foo}
  version{3}
  house{
   door{yes}
   window{no}
  }
}

... then an item can be fetched with their full names lile 'foo.name' or
'bar.house.door' and it allows traversing "directories" to get all the items
in the 'bar.house' directory etc.

In other words, if I knew some requirements I would consider taking on the
config file parsing.

-- 
      Daniel Stenberg - http://daniel.haxx.se - +46-705-44 31 77
   ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol

Re: config file q

Posted by Greg Stein <gs...@lyra.org>.
On Thu, Sep 14, 2000 at 09:16:04AM +0200, Daniel Stenberg wrote:
> quote from "notes/svn-config-files":
> 
>   Let's rethink this, and create a system which allows "nesty" syntax,
>   something like scheme.
> 
>   The main point is still to define sections/keys/vals.
> 
> I'm not fully aware about for what the config files are gonna be used and for
> what contents,

Subversion no longer has any config files. What we used to have on the
server has been subsumed within the Apache config file (although, I believe
that we'll also want to allow the directives to occur within .htaccess
files).

We *may* end up with a very simple config file that is part of the SVN
installation on the server. That would live in /etc/svn.conf or something,
and would be specific to the install rather than per-project type stuff. But
we haven't seen a need for it yet.

We do have some persistent stuff, but that is different from
(user-performed) configuration. And we're using XML for those files.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/