Alan Barrett wrote on Thu, Dec 23, 2010 at 17:34:09 +0200: > On Thu, 23 Dec 2010, Stefan Sperling wrote: > > I don't think there is an official way to prevent the config dir from > > being created. I'd be interested to know why you need this. What is > > your use case? > > The event that made me notice the problem was cron job owned by root, > whose command was something like "su serviceuser -c 'svn update > /path/to/dir'". Think of updating a working copy that contains the
And if you undefine $HOME? sudo -u serviceuser env -u HOME svn update /path/to/dir > files used by a web server. The svn update command runs in a context > where $HOME is root's home directory, and serviceuser is not even > allowed to write there, and might not even be allowed to read, so I got > an error or warning (I forget which, and the details change according to > the permissions). > > You ask why I need to avoid creating a .subversion directory, and I > suppose that I don't absolutely need to avoid creating it, but I also > don't need *to* create it (it won't contain any useful information), and > I don't want the clutter. > > Another annoying issue is that commands that one would expect to be > read-only (such as "svn status" or "svn info") also create the config > directory. > > --apb (Alan Barrett)
