Comment 30 for bug 109114

I do not see why a version system should dictate what the "core usage" of
a tool is. I work in forensic software development and it's very normal to
attach test files that are hundreds of MB's to a gigabyte if it is really
needed for the software.

BZR works great, I use it with great pleasure but I am always using it
with caution because I know of the memory limitation. This should not be
the case. If all files are "kept" in memory before storing couldn't you
just make a memory file on disk and take the slower check in for granted?

Another use case I have for BZR if it is taking large mem files is
versioning my personal data and media. Because BZR conveniently only keeps
one .BZR folder all my personal files are not cluttered. With one bzr
command the missing files can be added, and the deleted files removed. I
love that. And I will store the repository on a USB disk to keep a
versioned backup. But indeed, some files fail because they are too big.

With regards,
- Jorgen

On Mon, 28 Jun 2010 06:35:03 -0000, Martin Pool <email address hidden>
wrote:
> Memory usage has improved quite a bit in 2.2beta so you might like to
> test that. Versioning files of hundreds of MB on a machine with a few
> GB should now be quite feasible, but we still don't consider it as a
> core use case. bzr is for versioning source, not ISOs.
>
> --
> Martin