Re: Creating a new working copy in an existing directory (/etc)

On 30 Mar 2003, Nicolas Bonnefon wrote:

> Maybe an option should be added to forbid 'svn co' to actually overwrite
> controlled files? Or better: 'svn switch' may be allowed to work even
> with a directory which is not a working copy (adding the right infos)?

Hmm... I could not say how big change this kind of would be. And the need
for this is quite specific.

> > In my setup, there is also a file where is pretty printed my etc's
> > symlinks layout, and that file is also under version control.
>
> Fine, do you have a script to generate this file?

Yep, shameless find+sed+sort. My ls generates output like that:
$ ls -l /etc/passwd
-rw-r--r-- 1 root root 1929 2003-03-11 23:16 /etc/passwd

And here is the script:

#!/bin/sh
etc_links=/etc/etc_links.dat

find /etc -type l -exec ls -l {} \; | \
        sed 's/.*[0-9][0-9][0-9][0-9]-[0-9][0-9]-[0-9][0-9] [0-9][0-9]:[0-9][0-9] //'| \
        sort > $etc_links

Does anybody know how I would tell to gnu's ls that it should print out
only reference info of the symlink, and nothing more? Or is the 'symlinks'
the way to go?

> Regarding /etc, I had another idea to avoid messing up the /etc
> directory with subversion infos: we may put the svn controlled files in
> a subdirectory (a working copy) and only put symlinks to them in /etc.

I won't do that. I could almost promise to you that sometime, somehow
this will broke. Trust me. =)

BR, Jani

-- 
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org