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

Git as a BuildRequires (packaging)

From
JBJosh Boyer <jwboyer@gmail.com>
Date
Dec 2, 2008, 02:30 UTC
Message-ID
<20081202023004.GA30372@zod.rchland.ibm.com>
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

Next: Jeff King
Message 1 of 3 in “Git as a BuildRequires (packaging)”
  1. Josh BoyerDec 2, 2008
  2. Jeff KingDec 2, 2008
  3. Miklos VajnaDec 2, 2008

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.