nested and partial tree

[William Dode]

On 24-08-2006, John Arbash Meinel wrote:
> This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
> --------------enig4DC1AB503546ADBF95575351
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
>
> William Dode wrote:
>> Hi,
>>=20
>> I would like your advice for this situation.
>>=20
>> I've somes projects that are libraries in differents versions, theses=20
>> project contains the code of the library but also documentation,=20
>> tests...
>> I've somes projects that use theses libraries but need only the code of=
>=20
>> the libraries.
>>=20
>> Example of a library :
>
> It is funny to see '\', '~' and symlinks discussed at the same time.
> Since only Windows uses '\' as a directory separator.

Yes ! it's the vmware syndrome !

>
...
>
> So as you mentioned you are asking for both a nested and a partial 
> tree.
> In that you want to checkout part of another tree (partial) and put that
> underneath another tree (nested).
>
> Partial checkouts are something that need a lot of discussion, to decide
> exactly how/if we want to support it. The issue is that you end up
> committing trees that have never been fully tested. And it means that
> the tree *you* have checked out, may not match the tree someone else
> checks out from the same revision.

I think partial checkout should be read-only, but it's maybe not the 
scope of bazaar...

>
> Nested trees we already have limited support for. And Aaron is working
> hard to make the support much more seamless. So I would recommend:
>
> myproject/proj
> 	code/ # your stuff
> 	ext/ #Other stuff
> 	    libfoo-1.0/.bzr/
> 	        lib/
> 	        data/
> 	libs/
> 	    libfoo@ =3D> ../ext/libfoo-1.0/lib
>
> Another alternative, especially when we get better nested tree support,
> is that the 'lib' project itself could be several independent branches.
> A 'lib-tests', 'lib-docs', and 'lib-source'. I don't recommend it 100%
> at this point, but if you decide to do it the 'config-manager' project
> might work very well for you. It lets you specify a list of what needs
> to be checked out to get a working project. It even lets you do
> checkouts from different source formats. So it will let you do a SVN
> checkout of one library, as a sub directory of your bzr project, etc.

thanks, you confirmed what i thought

-- 
William Dodé - http://flibuste.net