From: Junio C Hamano <junkio@cox.net>
To: Jon Loeliger <jdl@freescale.com>
Cc: git@vger.kernel.org
Subject: Re: Question Building Deb Packages
Date: Mon, 21 Nov 2005 21:01:49 -0800 [thread overview]
Message-ID: <7vr799i8ci.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <E1EeOHi-0007Bx-HH@jdl.com> (Jon Loeliger's message of "Mon, 21 Nov 2005 20:53:30 -0600")
Jon Loeliger <jdl@freescale.com> writes:
> It _appears_ that the "deb" make target requires it to be
> done in an actual git repository.
I think we could cheat:
$ tar zxf original-tarball-of-0.99.9j.tar.gz
$ cd there
$ fakeroot debian/rules binary
But you are right; "make deb" at the toplevel would not work
well on a virgin machine, because it uses git-tar-tree to do the
tarball construction; we inherited this braindamage from RPM
building procedure. So if you do not want to cheat:
$ tar zxf original-tarball-of-0.99.9j.tar.gz
$ cd there
$ make install ;# to install in $HOME/bin
$ cd ..
$ git clone git://kernel.org/pub/scm/git/git.git/
$ git checkout -b build v0.99.9j
$ make deb
Then install the resulting deb and get rid of $HOME/bin/git*.
prev parent reply other threads:[~2005-11-22 5:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 2:53 Question Building Deb Packages Jon Loeliger
2005-11-22 5:01 ` Junio C Hamano [this message]
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=7vr799i8ci.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=jdl@freescale.com \
/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).