On Sun, Mar 07, 2010 at 11:27:35AM +0100, Paul Menzel <pm.debian@xxxxxxxxxxxxxx> wrote: > > 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. ;-) ]
Attachment:
pgpSxNFCfQTeR.pgp
Description: PGP signature