[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Storing configuration in repository directories

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: 2007-07-26 22:54:28 CEST

On Jul 26, 2007, at 09:00, david.x.grierson@jpmorgan.com wrote:

> Is there any particular reason why *repository* meta-data (as
> opposed to
> meta-data associated with the contents) shouldn't be stored in the
> repository directory?
> I'm thinking of recording repository ownership and project team
> membership
> information in one or more files either directly in the repository
> directory or in a sub-directory of it.
> For example you would have
> .../myRepo/ -+- .repoMeta/ <- this would be my new dir.
> +- README.txt
> +- conf/
> +- dav/
> +- db/
> +- format
> +- hooks/
> +- locks/
> For example would performing a dump fail if it found objects within
> the
> repository directory that it wasn't expect? What about other system
> commands (svnadmin verify)?

It's fairly common to put the conf and hooks directories into a
section of the repository, and make those directories working copies,
which could even auto-update themselves using a post-commit hook.
There is no problem doing this, or storing any other data in your
repository. You would probably not, however, want to store any of the
other files or directories you listed above in the repository, as
that would not make sense.

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jul 26 22:53:46 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.