Can somebody give me advice on moving to stacked branches?
Patrick van der Velde
petrikvandervelde at gmail.com
Sun Jun 7 06:04:39 BST 2009
Hi All
I am currently starting a new software project in .NET. This project
consists of several different parts (each of which may have one or
more assemblies). The current project tree looks roughly like:
project
bin
doc
lib
modules
core
...
...
src
plugins
...
...
src
ui
...
...
src
utils
...
...
src
tools
The source files for all the different parts live in the src
directories. I am currently thinking that I want / need to evolve the
different parts in different ways which would mean they would have to
be in separate repositories (have to might be a bit strong but it
would probably be convenient). Also the utils library should really
not be compiled into an assembly but the source files should directly
be linked into the other parts. So now I'm wondering if stacked
branches would help me with this. Could I do the following thing?
project
bin
doc
lib
modules
core <-- stack the core project here
plugins <-- stack the plugins project here
ui <-- stack the ui project here
tools
And then the individual projects will look like:
core
bin
lib
src
project1
project2
utils <-- utils project src stacked here
tools
Would this be a good way of doing this or are there other (better)
ways of organizing the project structure. The final goal is to be able
to build the parts separately but also to be able to build the whole
thing in one go (using a master build script).
Also if this is a good approach could somebody give me some
suggestions on how to do the following things:
1) I already have a (short) history in the current project, not much
stuff but if in anyway possible I'd like to keep the histories of the
different projects when I extract them
2) how do I setup the stacked branches, the documentation on the bzr
wiki doesn't really make things clear here and I don't want to screw
up my repository.
Thanks
Patrick
More information about the bazaar
mailing list