git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@gmail.com>
To: git@vger.kernel.org
Cc: skvidal@fedoraproject.org
Subject: Git as a BuildRequires (packaging)
Date: Mon, 1 Dec 2008 21:30:04 -0500	[thread overview]
Message-ID: <20081202023004.GA30372@zod.rchland.ibm.com> (raw)

Hi All,

Recently we've hit an issue where a new package being reviewed for
Fedora (cgit) needs to build against the git headers.  The problem
is that these headers aren't typically installed with the git
package itself, and we have no git-devel subpackage either.  This
is mostly due to the fact that from what I can tell the upstream
git Makefile doesn't install the headers anywhere.

There are a few options here.  The first is to install the git
headers and create a git-devel subpackage.  That seems like
overkill, given that the git headers are generically named and
would have to be installed to something like /usr/include/git/.

The second option is to create a patch file that includes all
the needed headers and use that in the cgit package.  That is
sort of sub-optimal given that you'd have to keep checking
(and possibly regenerating) the patch for correctness every time
a new version of git comes out.

The third option is to include the entire git tarball as part of
the sources for the package.  That is pretty easily done with the
Fedora infrastructure, but isn't exactly clean from a packaging
standpoint.

So, what do the git gurus recommend?  I'm not sure if other
distros have tackled this problem before, but some kind of
commonality for the 'how do you package things that need to build
against git' question would be nice.

(Please CC me.  I can't remember if I'm still subscribed to the
git list or not.)

thx,
josh

             reply	other threads:[~2008-12-02  2:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-02  2:30 Josh Boyer [this message]
2008-12-02  3:09 ` Git as a BuildRequires (packaging) Jeff King
2008-12-02 10:12   ` Miklos Vajna

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=20081202023004.GA30372@zod.rchland.ibm.com \
    --to=jwboyer@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=skvidal@fedoraproject.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).