Sharing common code within Bazaar

[Nicholas Allen]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This can be done by creating a separate branch for each module. You have
to then commit to each module separately if you make changes to many
modules from one project. Also the project itself cannot be a branch.
Nested trees is a feature that will allow each project to be its own
branch and when you commit to the project it will commit to each of the
modules as well (and remember which versions of the modules it is
working with).

I'm not sure when nested trees will be available. Perhaps a developer
will be kind enough to let us know an estimated time schedule for that
feature?

cheers,

Nick

Wezyde wrote:
| I have been using SVN for quite some time now and I find it difficult
to share
| code between projects.  I believe Bazaar should work well for this,
but I have
| no experience with Bazaar or DVCS in general.
|
| My project is within a Windows environment.
|
| Here's an example.  I have 2 (or more projects) that are similar but
each have
| different requirements.  Some of the modules are identical across all
of the
| projects and some are hardware/requirement specific to a particular
product.
|
| Project A
|   - Core
|   - CustomA
|
| Project B
|   - Core
|   - CustomB
|
| If a development makes a change to the Core then all projects using
this core
| should get the updates.
|
| I would like to know the best way to implement this using Bazaar (if
it is the
| right tool for this).
|
| Any suggestions would be extremely appreciated.
|
|
|
|

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIiDTI1+i51gqqEGkRAvzfAJ9FhHybkUSqO/gD63brxSICB0cekgCfW0nv
lEl/76hubChYk9LlvjEf47A=
=ydqq
-----END PGP SIGNATURE-----