git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: status of libgit.a

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Mar 7, 2010, 12:18 UTC
Message-ID
<20100307121809.GS27414@genesis.frugalware.org>
In-Reply-To
<1267957655.3759.29.camel@mattotaupa>
On Sun, Mar 07, 2010 at 11:27:35AM +0100, Paul Menzel <pm.debian@googlemail.com> wrote:
Show 8 quoted lines
> > You really need to talk to upstream if you want this libgit.a.
> 
> could you please give an update on the status of libgit.a. For example
> cgit still could not be packaged yet for Debian [1] because of this bug
> [2].
> 
> cgit is used by a lot of projects out there, so I am wondering if the
> current libgit.a can be released in its current state.

libgit.a is not a public library, so it will never have a stable API/ABI. There is a libgit2 project which tries to do this, but it's far from complete:

http://repo.or.cz/w/libgit2.git
> By the way, is there a web site/page for libgit.a?
No, there isn't.
I think the only sane solution is what Fedora does as well:
http://cvs.fedoraproject.org/viewvc/devel/cgit/

When cgit-1.2.3 is released, have a look at its Makefile, check what Git version does it want and add the relevant Git source to the cgit source package.

[ I remember Debian did not support having multiple upstream sources / one source package, I hope this is no longer the situation. ;-) ]

Previous: Paul MenzelNext: Nguyen Thai Ngoc Duy
Message 2 of 5 in “status of libgit.a”
  1. Paul MenzelMar 7, 2010
  2. Miklos VajnaMar 7, 2010
  3. Nguyen Thai Ngoc DuyMar 7, 2010
  4. Dmitry PotapovMar 7, 2010
  5. Johannes SchindelinMar 7, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.