[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: supporting http proxy via a config file

From: Karl Fogel <kfogel_at_newton.ch.collab.net>
Date: 2002-03-12 21:43:24 CET

cmpilato@collab.net writes:
> Given different files as opposed to different sections of a single
> file, you can more quickly find the "section" you're looking for (no
> need to parse)", but perhaps more importantly, there may be some
> "sections" that are consistent for user across all the machines they
> work on (automatically adding --quiet to commands, for example), and
> some "sections" not (proxy stuff, for example). Using seperate files
> allows them to more easily keep pieces of their subversion config
> under version control, where they can share that "section" across all
> the machines they work on.

Hmmm, see your point... This no longer seems like a bikeshed to me,
but I now think the single config file is preferable, for a few

   * We can't really do cross-file variable expansion, so multiple
     files will probably mean repeated information, hard for the user
     to keep in sync.

   * In the multi-file way (in Greg's second .subversion/proxies
     example, for instance), we end up with section names based on
     user parameters. What if these conflict with Subversion-specific
     section names? This is easier to avoid in a single file, because
     the alternative to dividing by files is to divide by sections --
     leaving prefixes ("group1_") within a section to do further
     subdivision. While that's not perfect, at least it helps us
     restrict the user-affected namespace to something below the
     section level, which may make it easier to avoid accidental

   * It's somewhat simpler to implement the one-file way.

Your point about being able to version control some files and not
others is undeniable, there's definitely a tradeoff here; I just think
the balance still leans to single file.

I guess I'll do this: start down the single file road in the code,
while continuing to watch the list for feedback.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 12 21:33:47 2002

This is an archived mail posted to the Subversion Dev mailing list.