On Friday, Jul 18, 2003, at 11:13 America/Chicago, pll@lanminds.com
wrote:
>
> I went a different direction. Since I don't use a lot of links in my
> home dir, I organized all my dot-file/dot-dirs into versioned
> directories. When I check out my home dir to another system,
> I have a shell script in my ~/bin dir which creates symlinkss from
> $HOME to $HOME/.dot[files|dirs]/* and I'm done.
I do the same thing, and it works well for me also.
>
> But back to the OPs problem of maintaining /etc in svn. I've found
> it's just easier to import only the files you really care about into
> the repo, and set svn:ignore for those you don't want to know about.
For this, I also do symlinks from /etc to root's working copy. But that
means a few things:
- root's homedir (or wherever the working copy is) needs traverse
permissions for whatever users/groups the servers run as; you might not
like that.
- you need to be careful about a few config files.
/etc/openldap/slapd.conf can have the root DN password in it. In a
one-way hash, but still, crackers exist.
- root needs to be able to access the Subversion repository through
some ra_XXX mechanism.
You can use ra_dav...but not if you want the Apache config files in
there, because if you screw them up, you can't just "svn up" to get a
fresh version.
You can use ra_file...but root's default umask is restrictive enough
that other users can't mess with it, even if you put the repository in
a setgid directory (no group write). The umask shouldn't really be
messed with; it's there for a reason.
You can use ra_svn+ssh, sshing to a normal user. This is probably the
best solution, but it's kind of annoying to set up. You can still
version your Apache files without problem, and you don't have to screw
around with permissions a lot.
Good luck.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 19 01:00:49 2003