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 <celoserpa_at_gmail.com>
wrote:
> Thank you folks :)
>
>
> On Feb 16, 2008 11:26 PM, Ryan Schmidt <subversion-2008a_at_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.
> >
> >
> >
>
Received on 2008-02-17 16:25:32 CET