David Evans <dev...@macports.org> writes: > On 3/14/16 4:38 PM, Sean Farley wrote: >> 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. > > libgit2-glib is actually a subproject of and maintained as a component of > gitg. It only exists because libgit2 doesn't > provide the introspection data required by gitg which is written in vala.
Personal rant: something, something same repo. (pygit2 might even be worse in this regard) >> 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. > > libgit2 and libgit2-glib updated to version 0.24.0 in r146698 after a quick > response > from the gitg developers. > > Sorry you had to do this. Hopefully, we can coordinate better in the future. No worries. I think this is a great example of having per branch builds / code review before things go into main. _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
