You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Adrian May <ad...@blue-cell-networks.com> on 2005/02/10 16:57:36 UTC
Working copy without meta data
Hi there,
I have a genuine problem with the idea of all the metadata being mixed up in my working copy under those .svn directories, but perhaps there's a work around.
I'm working on a minature linux box with a CF card instead of a disk drive. There isnt much free space. I spend most of my time trying to get its wierd hardware to do what it says it should, so Im always developing on the box itself. I often mess with kernal modules and versions of basic distribution stuff, so I'd actually like to have the whole CF card version controlled. Hopefully the SVN client is not too big, but these pristine files are completely out of the question. Also, how do I get a release checkout that just has what I want to ship?
Why not put the meta info in a completely seperate tree that exactly mirrors the one being managed, and let the user choose where it should be. I need it elsewhere on the network, but others might prefer it on the same machine to save network traffic.
I dont know why this issue of minimising network traffic seems to take such overriding importance in the design of SVN - its nice to optimise things of course, but the time it takes to commit is just a gradual annoyance, wheras disk space can be a hard constraint.
Maybe I can get around this by developing on a bigger CF card than I ship, but I still need to know how to get a .svn-free checkout to ship.
Any advice or future perspectives would be greatly appreciated,
Ad.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Working copy without meta data
Posted by Ben Collins-Sussman <su...@collab.net>.
On Feb 10, 2005, at 10:57 AM, Adrian May wrote:
>
> Maybe I can get around this by developing on a bigger CF card than I
> ship, but I still need to know how to get a .svn-free checkout to
> ship.
'svn export' is like 'svn checkout', but it doesn't create any
working-copy metadata at all. You're left with a completely
unversioned tree, ready for distribution, packaging, whatever you want.
>
> Any advice or future perspectives would be greatly appreciated,
>
Your request to store .svn/ metadata outside the tree has come up many
times over the years. So has the request to make the .svn/ "pristine
copies" cache into an optional thing. Those things, however, would
involve a complete rewrite of libsvn_wc.so, and thus is a far-off svn
2.0 thing. There are already feature requests filed on these.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Working copy without meta data
Posted by Olaf Dietsche <ol...@olafdietsche.de>.
Adrian May <ad...@blue-cell-networks.com> writes:
[about disk space constraints]
You might want to look at svk <http://svk.elixus.org/>. Svk is a
client, which doesn't use .svn directories.
Regards, Olaf.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
RE: Working copy without meta data
Posted by Dale Worley <dw...@pingtel.com>.
> From: Adrian May [mailto:adrian.may@blue-cell-networks.com]
> I have a genuine problem with the idea of all the metadata
> being mixed up in my working copy under those .svn
> directories, but perhaps there's a work around.
One possible workaround is to keep a real WC on a disk on some sort of
support machine, and copy the working files between the WC and the CF card.
The Unison file synchronization utility would do a nice job of this, for
instance.
In regard to "Why do they do it that way?", the reasons seem (to me) to be
the same as for CVS -- each WC directory is self-contained, and every
subdirectory in a WC is a valid WC for a subtree of the source tree.
OTOH, how a WC is structured is entirely a decision by the Subversion
client -- if one rewrote the appropriate parts of the svn client, it could
organize the WC any way one wanted it to.
Dale
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org