Re: libgit2 - a true git library

From: Steve Frécinaux <nudrema@gmail.com>
Date: Nov 8, 2008, 13:26 UTC
Message-ID: <4915939B.1070306@gmail.com>
In-Reply-To: <20081031170704.GU14786@spearce.org>

Shawn O. Pearce wrote:

Show 10 quoted lines

> During the GitTogether we were kicking around the idea of a ground-up
> implementation of a Git library.  This may be easier than trying
> to grind down git.git into a library, as we aren't tied to any
> of the current global state baggage or the current die() based
> error handling.
> 
> I've started an _extremely_ rough draft.  The code compiles into a
> libgit.a but it doesn't even implement what it describes in the API,
> let alone a working Git implementation.  Really what I'm trying to
> incite here is some discussion on what the API looks like.

Just a random question: is there a reason why you have put all the .h in a separate includes/ directory instead of relying on the install target to put the include files at the right place ?

To me it makes it much harder to hack on the files as one is always required to switch between both directories...