Re: [anjuta-devel] Git plugin libgit2 porting status update

[Sébastien Granjoux <seb sfo free fr>]

Hi James,


Le 08/08/2013 06:25, James Liggett a écrit :
> This is a pretty long message, so please bear with me here... :-)

I rather like long message, so thank for it.


Then, on the main topic. I haven't looked at libgit2 but I trust you and 
I think that using another library is not always the best solution 
especially when you replace some already working code.


> 1. Libgit2 is much too low-level for our needs; even implementing simple
> things like status are more complicated than they look
>
> 2. Many features we need are missing, especially things that depend on
> merge, including frequently-used features like pull.

I think these points can be solved by proposing some improvements in 
libgit2 itself or the target is to keep it very low level and move the 
high level part in another library?


> 3. Libgit2 needs to be compiled with special options to work well with
> our multithreaded environment. These issues may cause problems for our
> users, as they would be responsible for making sure their libgit2 is
> compiled with the right options.

I have done a quick search, it seems this thread option is only an issue 
on Windows. I suppose it can be enabled by default at least on Linux.


Anyway, is there some advantage for the end user to use libgit2? If not, 
I think we can wait (or help) until it becomes easier to use.


Regards,

Sébastien