Re: supporting http proxy via a config file

On Tue, Mar 12, 2002 at 03:11:37PM -0600, Karl Fogel wrote:
> Alan Langford <jal@ambitonline.com> writes:
> > $0.02 from a lurker... if you allow config files to include other
> > config files, and provide for variable expansion in the include file
> > path, then you have the advantages of both approaches.
>

This feature (variable expansion in the include file path) is something
that I haven't seen discussed. Maybe I've missed it. What I personally,
need is several different sets of proxy configurations: one for at home,
one for at work-site A, and one for at work-site B. Having multiple
includes would allow me to neatly separate out this complexity, but
I'd still need to be able to tell subversion "use HOME config", or "use
SITE-A config".

So, it seems like there are two options:
        1.) make the config file turing complete, and give it
        syscall access[*]

        2.) allow for some sort of getenv() expansion within
        the include path.

[*] Ha ha, only serious.

> True. Mike and I were discussing that on the phone just now, but it
> seemed like overkill -- more code to write bugs in, have to protect
> against recursive includes, bleargh. :-)
>

People who write recursive includes probably deserve what they get.

> However, if we start out with separate files, then it's always
> possible to add includes later...
>

Yes, but well-architected lexical scanners usually hide that
sort of thing from the rest of the system, anyway. Maybe that's
exactly what you're getting at...

- ben "#include <__FILE__>" king

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 12 22:13:30 2002