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

Re: many externals in a single directory

From: Ryan Schmidt <subversion-2007a_at_ryandesign.com>
Date: 2007-03-13 07:54:26 CET

On Mar 12, 2007, at 08:17, Tom Malia wrote:

>> On Mar 11, 2007, at 15:55, Elie Zananiri wrote:
>>> I would like to know if it is possible to have multiple externals
>>> all get downloaded to the same directory, and if so, how to do it.
>>> I tried the following syntax:
>>> code http://www.arepository.com/
>>> code http://www.asecondrepository.com/
>>> to have all external classes load in the "code" directory, but I
>>> think the second line overwrites the first because I only get files
>>> from the second repository in my "code" folder. And I can't put
>>> the files in subfolders because the compiler (Processing) can only
>>> find them if they're at the root of the "code" folder.
>> No, not possible with Subversion. Each external will get placed into
>> its own folder. The contents of your svn:externals property could be:
>> code1 http://www.arepository.com/
>> code2 http://www.asecondrepository.com/
> I was following this thread with some interest as I can see
> occasions where
> I might want to try to do the same thing.
> However, I think I'm beginning to understand why this isn't
> possibly and
> would like to ask the group for confirmation that my current
> understanding
> of the Subversion design is or is not correct.
> After messing with this product for about 3 or 4 days total now, I'm
> beginning to come to the realization that Subversion is basically
> "Folder
> Level" management. By which I mean, Subversion tracks changes to the
> content of a "Folder" not individual files, or rather, stores it's
> information about changes to files at the folder/directory level.
> Therefore, without a folder/directory Subversion really can't track
> changes.
> Also, Subversion assumes that the entire contents of a single
> folder in a
> working directory corresponds to one and only one folder in the
> repository.
> Therefore, managing changes strictly at the individual file level is
> basically not an option... would this be an accurate statement?

I think in a way, that's right. Subversion needs to store admin info
in the .svn directory within your working copy directory. If you
don't have a working copy directory, but only have a file, it has no
place to put its .svn info. If you wanted multiple externals to go
into a single directory, current Subversion would probably get quite
confused, since each external would expect to get complete control of
the contents of the .svn directory.

Related: you cannot check out a file -- the smallest unit you can
check out from a repo is a directory. (You can still export a single
file, if you just want to see its contents, but you can't then make
changes and check them back in.)

This is the existing enhancement request to be able to check out a
single file:


To reply to the mailing list, please use your mailer's Reply To All  
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 13 07:54:50 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.