git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Menzel <pm.debian@googlemail.com>
To: git@vger.kernel.org
Cc: Marc Oscar Singer <elf@synapse.com>, 407722@bugs.debian.org
Subject: status of libgit.a
Date: Sun, 07 Mar 2010 11:27:35 +0100	[thread overview]
Message-ID: <1267957655.3759.29.camel@mattotaupa> (raw)
In-Reply-To: <20090219092446.23272.qmail@3b5a9fa637f270.315fe32.mid.smarden.org>

[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]

Dear Git folks,


Am Donnerstag, den 19.02.2009, 09:24 +0000 schrieb Gerrit Pape:
> On Wed, Feb 18, 2009 at 09:10:02AM -0800, Marc Oscar Singer wrote:
> > Gerrit Pape wrote:

[…]

> > >It depends on upstream.  Back then, Junio asked to not provide such a
> > >library package in Debian, and I respect that.  There've been some plans
> > >and effort to stabilize the lib in the past, but I'm not sure about the
> > >status.
> > >  
> > Would it be a compromise to provide libgit.a as a static library for 
> > until it stabilizes?
> 
> That's not the compromise, that's the option, I don't know any plans
> about a shared library.  The git-core-dev package that was available for
> short included such a static library.
> 
> 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.

By the way, is there a web site/page for libgit.a?


Thanks and sorry if I got something wrong,

Paul


[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515793
[2] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=407722

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

       reply	other threads:[~2010-03-07 10:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <499B3F65.8010109@synapse.com>
     [not found] ` <20090218091617.7805.qmail@2684cdd72f0ee9.315fe32.mid.smarden.org>
     [not found]   ` <499C40EA.6050108@synapse.com>
     [not found]     ` <20090219092446.23272.qmail@3b5a9fa637f270.315fe32.mid.smarden.org>
2010-03-07 10:27       ` Paul Menzel [this message]
2010-03-07 12:18         ` status of libgit.a Miklos Vajna
2010-03-07 14:27           ` Nguyen Thai Ngoc Duy
2010-03-07 13:26         ` Dmitry Potapov
2010-03-07 16:36         ` Johannes Schindelin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1267957655.3759.29.camel@mattotaupa \
    --to=pm.debian@googlemail.com \
    --cc=407722@bugs.debian.org \
    --cc=elf@synapse.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).