-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> If I understand correctly, even with the svn:externals property, I
> would have to somehow match revision numbers of shared projects and
> applications.
>
> Say this is the organization:
> - rep1/shared
> sh1
> sh2
>
> - rep2/project1
>
> Now, when I need revision 341 of project1 repository, I must be
> aware that it
> used revision 15 of shared repository. If there are other repositories
> (like separate repositories for each third party library), the number
> of revisions to track will increase. Is my understanding correct, or
> can this be automated in some way?
You can store a specific repository revision in the svn:externals
property, so that every time you check out that revision you will get
the correctly matching shared project revision. On the other hand,
that can get fairly unwieldy if the the shared project changes often,
but it might be practical for tags (so, in the main trunk you could
keep the svn:externals property without a specific revision, so it
refers to the head, but then when you tag it, change the property to
refer to a specific revision---it probably wouldn't be too hard to
write a script for creating a tag that would do both steps together,
automatically).
- -Bill
>
> Regards,
> Bojan Resnik
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
iD8DBQFBQ0GXSwe0AHUdEwQRAt/NAKCRv2ucDYM9i2b6oewDxr6AxyoCNwCeNveh
DUu+Z50uVeCzZzFYaH8ZXnI=
=bWEU
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Sep 11 20:19:44 2004