Question about externals for this "unversioned files" discussion.
If I in revision 10 of my project add an external reference to another
directory on the same server, in the same repository, and then keep that
external there for the rest of my projects life, then... if I now, on
revision 100+ go back and do a checkout of a previous copy (after revision
10) of my project to a new directory, does the revision of the files in the
external working copy match the revision of my project working copy or will
it pick HEAD?
In other words...
/ <-- my project, mapped to svn://server/main
/lib <-- external, mapped to /svn/server/lib
if I change and commit files in main up to version 100, and sometimes update
files in lib as well, let's say for simplicity that the lib was created for
revision 10, and changed at revision 50 and 100.
If I checkout a HEAD working copy today, of revision 110, to a directory, I
/ <-- svn://server/main_at_110
/lib <-- svn://server/lib_at_110
however, what about going back and checking out, say, revision 25?
/ <-- svn://server/main_at_25
/lib <-- svn://server/lib_at_25 or 110?
if the external would get the HEAD revision, unless pegged, wouldn't this
match what the original poster want, albeit not exactly as smooth as he
wants it, if I understand him correctly?
Or perhaps I'm wrong, and it will get revision 25...
If so, then the question begs itself, what if the external is to another
server where I have no control? I would assume it could only, as a rule,
pick whatever is there at the moment, since it had no idea what was there at
On Wed, Mar 12, 2008 at 8:17 PM, Ryan Schmidt <
> On Mar 12, 2008, at 10:43, Mad Scientist wrote:
> > As another option could be adjusting svn:external to work with http/
> > ftp links to external files. Which could offer much of the
> > functionality of unversioned files in the repository while being
> > simpler to implement but could have its own problems if a
> > repository is moved or the site goes down/moved.
> That's... an interesting suggestion...
> Of course you have to replace "links to external files" with "links
> to external directories" since externals work on the file level, not
> the directory level; there's an existing enhancement request about that:
> Could be a bit tricky, since externals of course already support http
> links when that link is within a repository...
> Also even trickier because http URLs may not offer a directory
> listing, or if they do, the format is not predictable. That might be
> a show-stopper. Might have to wait for #937 to be implemented, and
> then restrict non-repository http links to single files, before this
> can be considered.
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
Lasse Vågsæther Karlsen
PGP KeyID: 0xBCDEA2E3
Received on 2008-03-12 22:00:34 CET