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

Re: Is it possible to distribute a folder with an edited .svn directory

From: David Weintraub <qazwart_at_gmail.com>
Date: Thu, 26 Feb 2009 11:19:49 -0500

In theory, it should work. All of the checkout information is in the
working directory. The .svn sub-directories have the URL of the
checkout, the files, and datestamps. The authorizations are stored in
your .subversion directory under your $HOME directory, so unlike CVS,
users won't have a problem due to authorization issues. I've moved
directories from computer to computer before without any problems.
There is an issue of who owns the files. Of course, most archive
utilities will handle that for you when it unpacks the archive.

But what does that really buy you?

If the purpose is to supply a sparse checkout, I would look at the
structure of your repository and see why you need sparse checkouts.
For example, one place where I worked had a giant Ant file to build
everything in the root of the directory, but each sub-directory was
its own independent project. Developers would checkout the root
directory, then the sub-project they wanted. I simply added separate
Ant build files to each project, and the root directory's Ant file
simply called each project's build file sequentially. That eliminated
the need for the sparse checkout.

Even if you do have something like a sparse checkout that makes doing
an "svn co" a bit harder than normal, you could have a simple shell
script that does it for you.

Otherwise, you'll get your users use to the idea of passing around
working directories to each other, or using that initial working
directory six months from now when everything has changed.

Developers should know their way around the tools they are using. I
insist that they learn to use the Subversion command line even though
most of them will be doing all of their checkouts via Eclipse or
TortuousSVN. I simply want them to understand what is going on, so
they don't come screaming to me whenever they get some minor error
message, or need to do something a bit out of the ordinary.

On Wed, Feb 25, 2009 at 11:15 AM, Merul Patel <merul.patel_at_gmail.com> wrote:
> I'm wondering whether it's possible to simplify the process for
> collaborators to setup their own working copy of a repository by
> downloading a ZIP archive that contains a partial working copy.
> The partial working copy would contain a folder to represent the root
> of the repository they want to check out, and then a .svn directory
> configured with the URL of the repository.
> They could then simply do an SVN update on that directory to fetch the
> entire contents of the repo. Is this possible at all?
> Thanks,
> Merul
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1227517
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].

David Weintraub
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-26 17:20:55 CET

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.