One big project with multiple small projects

[Lionel Dricot]

I agree that svn:external is not really friendly and that I personnaly hate
it. That's why I was hoping to have another solution for that in bzr.

As I cannot wait for nested tree, I see the following workaround :

One repository called "main" that will contain the core stuff and a script
called update that will call bzr branch for each of the modules

It's really not nice but at least, it should work.

On Mon, Dec 1, 2008 at 4:44 PM, Nicholas Allen
<nicholas.allen at ableton.com>wrote:

> It may not be easy to use but it is possible. But svn:externals is not
> really the right solution for the problem either. bzr nested trees is the
> only way to go. I just hope it happens sooner rather than later...
>
> Nick
>
>  afaik svn:externals (which Lionel was asking about) doesn't make that
>> very easy either. If you would like to follow specific revisions rather
>> than the latest revision of the external, you have to edit the
>> svn:externals property manually each time and set the revision that it
>> should use.
>>
>> Cheers,
>>
>> Jelmer
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20081201/fb91cf17/attachment-0001.htm