Hi Ryan,
Thanks for the link. I had not noticed that chapter...
I think my scenario is slightly different. We have many projects being
developed at the same time. For security and maintenance reasons, each
project is in a separate repository and we use external dependencies
every time it is necessary. We also keep the third-party libraries in
separate repositories so that they can be shared by more than one of our
projects.
Most of the third-party libraries we use are in binary form (libs,
dlls). To avoid versioning problems I want to make sure that each
revision is an exact snapshot of the library release.
Thanks,
Antao
Ryan Schmidt wrote:
>
> On Oct 16, 2006, at 12:47, Antao Almada wrote:
>
>> I'm keeping all the third-party libraries I use in separate
>> repositories. I then reference these from my project repositories
>> using externals. This way I'm sure that any revision number, tag and
>> branche will compile with the correct library version.
>>
>> I'm just not sure what's the best procedure to upgrade the library
>> version. Is it possible to do it in one single revision increment?
>> Like an import into a revision number?
>
> Have you read the chapter on vendor branches?
>
> http://svnbook.red-bean.com/en/1.2/svn.advanced.vendorbr.html
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Oct 17 16:00:49 2006