Re: Using Subversion to Maintain hooks & conf Directories

On 8/24/07, Andy Levy <andy.levy@gmail.com> wrote:
> On 8/24/07, Hilco Wijbenga <hilco.wijbenga@gmail.com> wrote:
> > Have you tried putting /var/svn/repo under version control? (I'm lazy
> > and that would save me from having to check out twice. It would also
> > be slightly easier to explain to other developers.)
>
> Put the entire repository into itself? That might cause the universe
> to implode :)

I take it you consider the universe imploding to be a Bad Thing(TM)? ;-)

> (I'm on Windows)

Your universe has already imploded then, hasn't it? :-P

> cd \repos (repos is where I keep my repositories)
> svnadmin create recursion
> cd recursion
> svn co file:///c:/repos/recursion .
> svn add .
> svn ci -m "let's have some fun"
> C:\repos\recursion>svn st
> ? db\revs\1
> ? db\revprops\1
> M db\current

<snip/>

> This should probably be put in the "not a good idea" bin.

As I already said: you'd exclude db, dav, and locks using svn:ignore.
Obviously you can't do what you just did. :-)

But I'd like to have both hooks and conf under version control in,
say, directory my_repo_stuff. Then checking out my_repo_stuff (in
/var/svn/repo) would give me just hooks and conf ... and a .svn
directory. I'm just not sure whether Subversion cares if I have extra
directories lying around in /var/svn/repo especially Subversion
directories.

Cheers,
Hilco

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Aug 24 19:54:25 2007