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

SASL section of svnserve.conf: generate conditionally or always?

From: David Glasser <glasser_at_davidglasser.net>
Date: Thu, 3 Apr 2008 10:54:21 -0700

Currently we generate the SASL section of svnserve.conf if and only if
SVN_HAS_SASL is set: that is, if "svnadmin" (at the time of running
"svnadmin create") is linked with SASL.

However, if the svnadmin used to create the repository and the
svnserve used to serve it come from different builds (perhaps because
the repository was created long before you considered serving it with
SASL), this choice could be wrong: the config file might say that SASL
will work when svnserve isn't actually built with it, or the config
file might not mention SASL at all even though you now have a
SASL-enabled svnserve.

Should we change the generated file to always talk about SASL but
direct the user to check the output of "svnserve --version" to see if
SASL authentication is available?

(Similar issues will hold for the generated fsfs.conf I'm about to add
on the in-memory-cache branch w.r.t. apr_memcache.)


David Glasser | glasser@davidglasser.net | http://www.davidglasser.net/
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-04-03 19:54:38 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.