You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Marcelo de Moraes Serpa <ce...@gmail.com> on 2008/02/16 19:42:23 UTC

Tags and svn:externals

Hello list,

I'm just about to create a tag of the first release of my application.
However, it uses several external packages that I also commit regularly from
within the app repository itself (it is more practical).

Will the copy command also copy a snapshot of the svn:externals package? (I
guess not) - so, is it better to copy the working copy directory snapshot to
the tag?

Any suggestions?

Thanks,

Marcelo.

Re: Tags and svn:externals

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Feb 17, 2008, at 09:25, Marcelo de Moraes Serpa wrote:

> Oh... something just came into my mind: What about copying the  
> entire working copy to the tag (so, it will also copy the files  
> fetched via svn:externals) ? I guess it would be better to use the - 
> r since this approach would have the same result but would only  
> result in more bloat in the repo...

svn does not consider the external directory to be a part of the  
working copy. So using svn cp to copy the working copy somewhere will  
only copy the files of the primary working copy, not the files  
fetched via the external definition. The external definition will  
still be in the working copy, of course, so that when you next check  
out from this tag, the external definition will be acted upon and the  
external files will be fetched from the external location. If that  
external location does not include a revision number, then what's  
fetched to the external directory when the tag is checked out might  
not match what was in the external when the tag was made. Hence, use  
svncopy.pl.

> On Feb 17, 2008 12:24 PM, Marcelo de Moraes Serpa wrote:
> Thank you folks :)
>
>
> On Feb 16, 2008 11:26 PM, Ryan Schmidt wrote:
>
> On Feb 16, 2008, at 18:41, Blair Zajac wrote:
>
> > Marcelo de Moraes Serpa wrote:
> >>
> >
> >> I'm just about to create a tag of the first release of my
> >> application. However, it uses several external packages that I
> >> also commit regularly from within the app repository itself (it is
> >> more practical).
> >> Will the copy command also copy a snapshot of the svn:externals
> >> package? (I guess not) - so, is it better to copy the working copy
> >> directory snapshot to the tag?
> >> Any suggestions?
> >> Thanks,
> >> Marcelo.
> >
> > The copy will copy the exact svn:externals property so a checkout
> > from the tag will do a checkout of the external.
> >
> > So if you don't have a -r N in the external, then the tag will
> > continue to pick up HEAD of the external.  So people normally put
> > in an explicit revision in the external when they tag it so that
> > the tag doesn't pick up newer commits.
>
> Or you can use the svncopy.pl script to create the tag, which will
> add the -r argument to the external definition when it makes the tag.
>
>
>
>


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

Re: Tags and svn:externals

Posted by Marcelo de Moraes Serpa <ce...@gmail.com>.
Oh... something just came into my mind: What about copying the entire
working copy to the tag (so, it will also copy the files fetched via
svn:externals) ? I guess it would be better to use the -r since this
approach would have the same result but would only result in more bloat in
the repo...

On Feb 17, 2008 12:24 PM, Marcelo de Moraes Serpa <ce...@gmail.com>
wrote:

> Thank you folks :)
>
>
> On Feb 16, 2008 11:26 PM, Ryan Schmidt <su...@ryandesign.com>
> wrote:
>
> >
> > On Feb 16, 2008, at 18:41, Blair Zajac wrote:
> >
> > > Marcelo de Moraes Serpa wrote:
> > >>
> > >
> > >> I'm just about to create a tag of the first release of my
> > >> application. However, it uses several external packages that I
> > >> also commit regularly from within the app repository itself (it is
> > >> more practical).
> > >> Will the copy command also copy a snapshot of the svn:externals
> > >> package? (I guess not) - so, is it better to copy the working copy
> > >> directory snapshot to the tag?
> > >> Any suggestions?
> > >> Thanks,
> > >> Marcelo.
> > >
> > > The copy will copy the exact svn:externals property so a checkout
> > > from the tag will do a checkout of the external.
> > >
> > > So if you don't have a -r N in the external, then the tag will
> > > continue to pick up HEAD of the external.  So people normally put
> > > in an explicit revision in the external when they tag it so that
> > > the tag doesn't pick up newer commits.
> >
> > Or you can use the svncopy.pl script to create the tag, which will
> > add the -r argument to the external definition when it makes the tag.
> >
> >
> >
>

Re: Tags and svn:externals

Posted by Marcelo de Moraes Serpa <ce...@gmail.com>.
Thank you folks :)

On Feb 16, 2008 11:26 PM, Ryan Schmidt <su...@ryandesign.com>
wrote:

>
> On Feb 16, 2008, at 18:41, Blair Zajac wrote:
>
> > Marcelo de Moraes Serpa wrote:
> >>
> >
> >> I'm just about to create a tag of the first release of my
> >> application. However, it uses several external packages that I
> >> also commit regularly from within the app repository itself (it is
> >> more practical).
> >> Will the copy command also copy a snapshot of the svn:externals
> >> package? (I guess not) - so, is it better to copy the working copy
> >> directory snapshot to the tag?
> >> Any suggestions?
> >> Thanks,
> >> Marcelo.
> >
> > The copy will copy the exact svn:externals property so a checkout
> > from the tag will do a checkout of the external.
> >
> > So if you don't have a -r N in the external, then the tag will
> > continue to pick up HEAD of the external.  So people normally put
> > in an explicit revision in the external when they tag it so that
> > the tag doesn't pick up newer commits.
>
> Or you can use the svncopy.pl script to create the tag, which will
> add the -r argument to the external definition when it makes the tag.
>
>
>

Re: Tags and svn:externals

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Feb 16, 2008, at 18:41, Blair Zajac wrote:

> Marcelo de Moraes Serpa wrote:
>>
>
>> I'm just about to create a tag of the first release of my  
>> application. However, it uses several external packages that I  
>> also commit regularly from within the app repository itself (it is  
>> more practical).
>> Will the copy command also copy a snapshot of the svn:externals  
>> package? (I guess not) - so, is it better to copy the working copy  
>> directory snapshot to the tag?
>> Any suggestions?
>> Thanks,
>> Marcelo.
>
> The copy will copy the exact svn:externals property so a checkout  
> from the tag will do a checkout of the external.
>
> So if you don't have a -r N in the external, then the tag will  
> continue to pick up HEAD of the external.  So people normally put  
> in an explicit revision in the external when they tag it so that  
> the tag doesn't pick up newer commits.

Or you can use the svncopy.pl script to create the tag, which will  
add the -r argument to the external definition when it makes the tag.



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

Re: Tags and svn:externals

Posted by Blair Zajac <bl...@orcaware.com>.
Marcelo de Moraes Serpa wrote:
> Hello list,
> 
> I'm just about to create a tag of the first release of my application. 
> However, it uses several external packages that I also commit regularly 
> from within the app repository itself (it is more practical).
> 
> Will the copy command also copy a snapshot of the svn:externals package? 
> (I guess not) - so, is it better to copy the working copy directory 
> snapshot to the tag?
> 
> Any suggestions?
> 
> Thanks,
> 
> Marcelo.

The copy will copy the exact svn:externals property so a checkout from the tag 
will do a checkout of the external.

So if you don't have a -r N in the external, then the tag will continue to pick 
up HEAD of the external.  So people normally put in an explicit revision in the 
external when they tag it so that the tag doesn't pick up newer commits.

Regards,
Blair

-- 
Blair Zajac, Ph.D.
CTO, OrcaWare Technologies
<bl...@orcaware.com>
Subversion training, consulting and support
http://www.orcaware.com/svn/

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