> I can also argue with the Principle of least astonishment: > > So say we've added a new svnadmin option --dont-create-svnserve- > config, > and we've made svnserve skip repositories which don't have an > svnserve.conf file within them (putting aside the still unsolved > problem > of what svnserve should do when run with a single global config > file).
Well, the next complaint would be... that should be the default since if I run svnadmin create I don't "know" I need to use that option. It all comes back to, imnsho, people expect to be able to use complex software without spending even a small amount of time reading documentation and understanding how stuff works. Is there really that much overhead in deleting the binary and insuring the correct permissions are used on the repository folders to "keep the honest, honest?" After all, any one with root/administrator access is able to bypass anything you've done anyway. It rather see the devs working on 1.7 WC features like a real "branch" command, performance, etc, rather than adding a config option that nobody will use. Also, if you want a more "secure" version of subversion package up your own binaries that don't include svnserve... let the svn dev's work on the stuff that we can't do with 3 or 4 lines of a batch/command file. BOb
