On Wed, 2005-07-20 at 15:59 +0200, VladimĂr Marek wrote:
> > This is A VERY BAD IDEA.
> > If you're working on more than one project, they will all share
> > metadata if the environment variable is
> > set.
>
> Well, it's true that you have to pay attention, but it's nothing hard.
> And the metadata directory could contain "it's" working copy path. (
> This is not bulletproof, but I think that I would work sufficiently )
I chose Subversion because the development team is not satisfied with
solutions that work 'sufficiently'.
The only way Open Source projects are going to really compete with
commercial products in commercial environments, is when they don't
accept 'sufficiently'.
No flame intended, I understand what you would like to do. Still it is a
bad idea. Not only because of what Tommy said, but also because there
already is a solution to your 'problem':
About a): If you want to create a tree of the dirs and files in your
repos for shipping to a customer, you can use svn export to export it.
Also, you could write a nice script for packaging stuff which also
removes .svn dirs along the way.
Your suggestion under b) about sharing a working copy over the network
is really *ugly* and makes me think you did not understand the concept
of version control or subversion. How are you ever going to say what the
version of a file is if people have seperate metadata about shared data?
Remember what metadata means: data about the data. Inconsistency all
over if you have multiple, *different* data on 'the data' (your working
copy).
About c). What about svnadmin dump? This is not a poor man's incremental
backup. It is no backup at all. Period.
Anyway, I hope you understand what I mean, and why your thoughts are
really not a good idea (although quite original I must say).
Good luck!
Pim
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jul 20 16:12:52 2005