On Jan 24, 2007, at 14:53, Janine Sisk wrote:
> On Jan 24, 2007, at 12:43 PM, Ryan Schmidt wrote:
>
>> Now the core directory will contain directories foo, bar and baz
>> which are taken from the trunks of those respective projects
>> within your repository. And it should be noted that the above was
>> just initial set-up that only had to be done once; now, any time
>> you check out core, it will automatically pull in foo, bar and baz
>> because of the externals definition.
>
> Thanks, Ryan, that's exactly what I had in mind. Except in my case
> the directories to be included are all in the same trunk. The idea
> is that there are core pieces that everyone needs to check out, and
> then there are other groupings of directories that one might or
> might not need depending on exactly what one is working on. It's
> much easier and less error prone to check these out via aliases.
>
>> Yes, any changes you make to foo, bar and baz within the core
>> working copy will have to be committed separately of one another.
>> Yes, that applies even though they're in the same working copy.
>
> Ouch, not so good. Is there any other way to accomplish this that
> would not have the restriction?
I believe an alternative would be to use "svn switch". You could
create /aliases/core and then svn mkdir various empty directories
inside it. There could be a README file at the top level explaining
what to do after checkout (or a setup.sh script to do it for you).
You would then need to "svn switch" each empty directory to the
correct place within the repository. Then I believe you can commit
everything at once. But this switching would need to be done each
time anyone checks out a new working copy.
P.S: Don't forget:
--
To reply to the mailing list, please use your mailer's Reply To All
function
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 24 22:16:09 2007