sean at macports.org
Mon Mar 14 16:38:20 PDT 2016
David Evans <devans at macports.org> writes:
> On 3/14/16 1:25 PM, Sean Farley wrote:
>> If I come off as arrogant, my apologies. I like to move fast and this
>> makes working with me difficult.
>> For what it's worth, I'm testing a script that automatically updates a
>> port so we can (potentially) have a bot that tries to update every
>> outdated port and report what breaks. This caused me to miss your
>> But I understand that not many people like working with me and my
>> efforts are rarely appreciated. Though I still think libgit2-glib is a
>> sorry excuse for a project.
> Sean, here's an update:
> I filed a ticket concerning this issue  and a number of updates have been committed to upstream git master in the
> last hour or so to fix the API break . gitg has now been updated to require libgit2-glib 0.23.11 so a new release
> should be available soon .
Thanks for following through!
libgit2 makes so many breaking api changes that its subprojects (pygit2,
libgit2-glib, etc.) should really be part of the same repo so that they
all get updated and released at the same time.
I've already forked pygit2 to download and install the corresponding
libgit2 version so that it can be installed into a virtualenv. Quite the
hack, but seems to work for now.
More information about the macports-dev