Out of Memory a bridge too far

[Chris Hecker]

>> What I am actually looking for (I believe) is something along the
>> lines of the new largefile support in Mercurial.
> Yes, we are interested in both helping you write it, and in getting
> it merged in to core.

My fear about doing a hacky "external largefile solution" like in hg is
that it will be "good enough" and relieve any pressure to solve the real
problem, but it's really a quite crappy solution to the actual problem.
 Solving it the right way seems like it would be only a little more work
(once you take into account testing and everything over the lifetime),
yet it would set bzr up to be a real "dvcs 2.0" project, leaving the
hacks behind.

Of course, I ranted about this before on this list, and since I don't
have time to do it myself, I guess it's just a bunch of hot air right now.

Chris


On 2011/11/12 01:36, Martin Pool wrote:
> On 12 November 2011 20:14, Jason Earl <jearl at notengoamigos.org> wrote:
>> However, I don't have Windows-specific problems with large files.  I am
>> a GNU/Linux user (Ubuntu actually), and I am working with a mixture of
>> source code and binary files up to about 500M or so.  My most
>> problematic project is comprised of a mixture of LaTeX and image files.
>> I will inevitably want to have larger files as well.
>>
>> What I am actually looking for (I believe) is something along the lines
>> of the new largefile support in Mercurial.  I want to be able to say
>> "this is a big binary file, treat it differently," and call it a day.
>> In a perfect world I would not only like to write something that I could
>> use, but something that would be accepted back into Bazaar.
>>
>> Unfortunately, I have no idea if the Bazaar developers would even be
>> interested in such a beast, much less how hard something like that would
>> be to write.
> 
> Yes, we are interested in both helping you write it, and in getting it
> merged in to core.
> 
> There was a thread back in July "binary file storage" where some of
> the options were discussed.
> 
> The simplest place to start, I think, is to just put them on a shared
> directory or http server somewhere and have a post_change_branch_tip
> hook that copies them in to the tree, if there is one.  That will let
> them be stored externally and then automatically inserted on check
> out.
> 
> m
>