Re: Best practise for large projects with many product "sub-units"

Frode Tenneboe wrote:
> On Wed, 2009-11-11 at 09:49 +0000, petermity wrote:
>
> Thank you for your input, Pete.
>
>> You didn't mention Externals Definitions - this might be part of the
>> solution to organizing and using SVN with your software. For instance 3PP
>> and libs could be separate independent SVN projects (repositories). Then
>> a project and/or product can pull pieces of those in as needed via
>> externals.
>
> It does indeed seem like the right tool for the job!!!
>
> How does it work in practise? When a user checks out a directory
> consisting of externals which are tagged, how can I easily mange locking
> to prevent them from being checked in to by a user who inadvertently
> updates local code without setting the correct path? Are there any
> tools to assist in the handling of externals?

Commits don't automatically recurse into externals. If you want to
change/commit something there you have to explicitly cd into the
directory. You might want a pre-commit hook that prevents modifying
existing tags just on general principles, though.

-- 
   Les Mikesell
    lesmikesell_at_gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2416613
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].