[Adium-devl] Let's switch to a DVCS

[Christopher Forsythe]

2009/4/15 Graham Booker <gbooker at cod3r.com>

>
> On Apr 15, 2009, at 12:55 PM, Evan Schoenberg wrote:
>
>  On Apr 15, 2009, at 11:17 AM, Zachary West <zacwest at gmail.com> wrote:
>>
>>  On Wed, Apr 15, 2009 at 11:12, Peter Hosey <boredzo at adiumx.com> wrote:
>>>
>>>> Full history includes branches. Omitting anything is not full history.
>>>>
>>>> Various tools have choked on it. Last I saw, though, hg convert was able
>>>> to
>>>> go all the way in several runs. Again, that's just my memory and I might
>>>> have forgotten a problem.
>>>>
>>>> I'm running it right now on my other machine, so we'll see what happens.
>>>>
>>>> It's 1.9 GiB.
>>>>
>>>
>>> The mercurial repository? I know svn is about that big, but if we're
>>> going to have to download that much to clone, I don't think we can
>>> manage.
>>>
>>
>> That's crazy big. Are we going to end up at those levels with any DVCS no
>> matter what over time given the libpurple binary? That might require
>> periodic pruning... Or is there a way to distribute only history from one
>> point forward?
>>
>
> Yeah, every DVCS is going to have about the same size.  I can tell you that
> when I was running a test of the Perian repository, I tried excluding the
> ffmpeg library binary that we used to have in there.  It significantly
> reduced the size, such that the repos was smaller than a checkout.  Perhaps
> a system where the libpurple binaries are separated from the rest of the
> source to keep it manageable?
>

You could keep the libpurple binary in an svn repo and write a script to
update the binary prior to building within xcode.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://adium.im/pipermail/devel_adium.im/attachments/20090415/bc94f3f0/attachment-0001.html>