You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Ryan Schmidt <su...@ryandesign.com> on 2008/03/12 19:17:25 UTC
Re: http/ftp links in svn:externals (was: Re: Unversioned files held by repo)
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:
http://subversion.tigris.org/issues/show_bug.cgi?id=937
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@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: http/ftp links in svn:externals (was: Re: Unversioned files
held by repo)
Posted by Matthew Hannigan <ml...@zip.com.au>.
On Wed, Mar 12, 2008 at 02:17:25PM -0500, Ryan Schmidt wrote:
>
> 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:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=937
>
> 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.
This requirement would probably be covered by Robert Collins' "config-manager"
It's in debian, but you can go to the source
The description is: "manage directories with Arch, CVS, HTTP, FTP and/or Subversion"
but I believe it does other vcs' including bzr.
The idea is that you place definitiions of dirs in a config file (e.g. get r1200 or HEAD
of a particular svn repo (or other vcs), and config-manager will fetch them.
It looks a little unmaintained; I'll try and get an update on it's rewrite to python.
http://www.robertcollins.net/config-manager.html
http://packages.debian.org/sid/config-manager
Matt
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: http/ftp links in svn:externals (was: Re: Unversioned files held by repo)
Posted by Lasse Vågsæther Karlsen <la...@vkarlsen.no>.
Just to be 100% sure, I tested it, and the external gets HEAD unless pegged.
On Wed, Mar 12, 2008 at 9:59 PM, Lasse Vågsæther Karlsen <la...@vkarlsen.no>
wrote:
> 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 would get:
>
> / <-- svn://server/main@110
> /lib <-- svn://server/lib@110
>
> however, what about going back and checking out, say, revision 25?
>
> / <-- svn://server/main@25
> /lib <-- svn://server/lib@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
> the time...
>
>
> On Wed, Mar 12, 2008 at 8:17 PM, Ryan Schmidt <
> subversion-2008a@ryandesign.com> wrote:
>
> >
> > 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:
> >
> > http://subversion.tigris.org/issues/show_bug.cgi?id=937
> >
> > 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@subversion.tigris.org
> > For additional commands, e-mail: users-help@subversion.tigris.org
> >
> >
>
>
> --
> Lasse Vågsæther Karlsen
> mailto:lasse@vkarlsen.no
> http://presentationmode.blogspot.com/
> PGP KeyID: 0xBCDEA2E3
--
Lasse Vågsæther Karlsen
mailto:lasse@vkarlsen.no
http://presentationmode.blogspot.com/
PGP KeyID: 0xBCDEA2E3
Re: http/ftp links in svn:externals (was: Re: Unversioned files held by repo)
Posted by Lasse Vågsæther Karlsen <la...@vkarlsen.no>.
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
would get:
/ <-- svn://server/main@110
/lib <-- svn://server/lib@110
however, what about going back and checking out, say, revision 25?
/ <-- svn://server/main@25
/lib <-- svn://server/lib@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
the time...
On Wed, Mar 12, 2008 at 8:17 PM, Ryan Schmidt <
subversion-2008a@ryandesign.com> wrote:
>
> 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:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=937
>
> 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@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
--
Lasse Vågsæther Karlsen
mailto:lasse@vkarlsen.no
http://presentationmode.blogspot.com/
PGP KeyID: 0xBCDEA2E3