Large repository support
Сюзев Кирилл
suzev.kirill at gmail.com
Thu Oct 21 10:54:38 BST 2010
2010/10/21 John Arbash Meinel <john at arbash-meinel.com>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
In bzr land, the best solution is usually to partition your tree. I
don't know your specific data, but I would doubt that you couldn't find
at least *some* partition points inside that 20GB of stuff. (Different
> applications, different libraries, data vs code, etc.) At which point,
> you have lots of smaller branches, and each one no longer has to be
> tree-wide atomic with all of the other content.
>
I thought about it, but look what happens. For example I have a trunk tree
like:
trunk/
dir1
dir2
....
dir20
Suppose, I need to make a feature and I'm going to change dir20 only, so I
branch dir20 and keep it somewhere. But programs in dir20 depends on other
dirs, so I have to create symlinks on other dirs near my branched dir20 to
make it looks like native environment. It's not very comfortable, and what
if I have several feature branches? I would have to repeat all this work
with symlinks again for each branch.
For example, git and hg do not have this issue, because they both can store
limited number of revisions.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.ubuntu.com/archives/bazaar/attachments/20101021/24b6398e/attachment.htm
More information about the bazaar
mailing list