Re: svn:externals and revisions

[Molle Bestefich <mo...@gmail.com>]

6/28/05, Norbert Unterberg <nu...@gmail.com> wrote:
> 2005/6/28, John Peacock <jp...@rowman.com>:
> > Ben Collins-Sussman wrote:
> > > Hm, this might be a bug.  What you're saying is that 'svn up -r X'
> > > updates the working copy to revision X, but updates the externals to HEAD?
> >
> > What other choice would you have Subversion make?  Externals can point
> > at a completely different repository, so there it is highly likely that
> > the same rev number has no correlation there.
> 
> This issue is coming up again and again. Are there any plans about a
> new property that is designed for this kind of requests, like
> "svn:internals" or a smarter "svn:externals" property that would
> accepts relative paths inside the same repository (so they survive
> branching and tagging)? It is not the first time that I would like
> something that fits the CVS virtual modules (were they called that
> way?) more closely than an svn:externals...

OMG, it would be wonderful to have this fixed.

I imagine that there are actually a whole lot more people that use
svn:externals for references to framework / core files internally in
the repository than there is people using it for it's original
purpose?  I've seen a lot of people use svn:external for internal refs
over on TSVN, but noone that use it to reference external
repositories.  Am I completely wrong?

We're getting bit by the svn:external design on a daily basis, and I
imagine others are too...  Here's some of the problems we've seen..

Problems:

- When tagging a project, svn:external'd files inside the tags
continue to update to HEAD (already mentioned) :-(..

- When changing the server name of the Subversion server, all of the
svn:external tags go dead :-(..

- When switching a WC from one URL to another, framework files are not
updated while everything else is.  You have to do an explicit 'svn up'
to get the framework files updated :-(..

- When updating a WC, a long list of "External: blah blah" lines are
output, which obscures the view and "hides" the interesting stuff, eg.
files that have been updated :-(..

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: svn:externals and revisions

[Molle Bestefich <mo...@gmail.com>]

7/7/05, Molle Bestefich <mo...@gmail.com> wrote:
> 6/28/05, Norbert Unterberg <nu...@gmail.com> wrote:
> > This issue is coming up again and again. Are there any plans about a
> > new property that is designed for this kind of requests, like
> > "svn:internals" or a smarter "svn:externals" property that would

> OMG, it would be wonderful to have this fixed.
> 
> I imagine that there are actually a whole lot more people that use
> svn:externals for references to framework / core files internally in
> the repository than there is people using it for it's original
> purpose?  I've seen a lot of people use svn:external for internal refs
> over on TSVN, but noone that use it to reference external
> repositories.  Am I completely wrong?
> 
> We're getting bit by the svn:external design on a daily basis, and I
> imagine others are too...  Here's some of the problems we've seen..
> 
> Problems:
> 
> - When tagging a project, svn:external'd files inside the tags
> continue to update to HEAD (already mentioned) :-(..
> 
> - When changing the server name of the Subversion server, all of the
> svn:external tags go dead :-(..

 - In the same ball park:  We're effectively locked with the SVN
access method that our current setup has - if we change it, all of the
external references will die :-O..

> 
> - When switching a WC from one URL to another, framework files are not
> updated while everything else is.  You have to do an explicit 'svn up'
> to get the framework files updated :-(..
> 
> - When updating a WC, a long list of "External: blah blah" lines are
> output, which obscures the view and "hides" the interesting stuff, eg.
> files that have been updated :-(..
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org