Josh Andler wrote:
Aaron Spike wrote:
> bulia byak wrote:
>
>
>> Bob,
>>
>> it's me again with the same request :)
>>
>>
Actually, I started using that last week. I'll upload it
tomorrow. The
last "fulldbg" build
used it, I think.
> I feel bad for Bob every time I see this. Let's have a
brainstorm. Is
> there any way we can unburden Bob? Can we setup some processes to allow
> this to be a distributed task, accomplishable by more than one person?
> Is there any way we could implement versioning and incremental updates
> (svn,rsync)? Or is the current arraignment satisfactory for everyone?
>
>
I'm completely with you on this. Especially because one of the most
common things we need updates on is cairo (more often than gtk it
seems). Plus, heaven forbid Adobe snags Bob too... ;) Our win32 users
would be up the creek then.
-Josh
I've always thought that some mechanism similar to Gentoo's (or wherever
they got it)
Portage would be excellent for keeping a win32 binary lib tree
constantly updated. Not
only would it be good for us, but we could share the burden/benefits
with other projects
with similar needs, like Gimp/win32.
For now, though, rsync does sound like it would do the trick, but svn
would be better
because of its ability to be versioned. For a release, we could tie a
devlibs version to
an Inkscape version. Transactions would be a bit slower; however, its
ability
to handle binary diffs would add some efficiencies.
bob