From: Ken Dreyer <kdreyer@redhat.com>
To: Robert LeBlanc <robert@leblancnet.us>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Build RPMs from git
Date: Wed, 10 Jun 2015 11:22:56 -0600 [thread overview]
Message-ID: <55787270.10101@redhat.com> (raw)
In-Reply-To: <CAANLjFprkpfMdCk5HKMtCt1r2y8Og+8p2b3BjgxsoYWynCV8oA@mail.gmail.com>
On 06/10/2015 09:44 AM, Robert LeBlanc wrote:
> This is really helpful, I was able to figure out what was needed in a
> tarball manually, but this is what I was really looking for to create
> the tarball.
>
> Is there anyway to skip this step like in the deb build for really
> fast builds? I guess if I don't have retar a dozen times to tweak
> something every time because I forgot to add something to the tarball,
> it won't be so bad...
There is a "make_dist.sh" script on master that is going to eventually
replace this "make dist-bzip2" step. It still requires you to repack a
whole new tarball, though.
Sorry I'm not very familiar with the way that the Debian builds straight
out of Git work. Reading through ceph-build.git and autobuild-ceph.git,
it's not using git-buildpackage. How are you doing it?
- Ken
next prev parent reply other threads:[~2015-06-10 17:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 21:15 Build RPMs from git Robert LeBlanc
2015-06-10 10:03 ` Brad Hubbard
[not found] ` <CAANLjFrgBDiVsRRUEfE3yvzieR7+4a0EBxxG8s9+buXi0T6HZg@mail.gmail.com>
2015-06-10 15:37 ` Fwd: " Robert LeBlanc
2015-06-10 14:30 ` Ken Dreyer
2015-06-10 15:44 ` Robert LeBlanc
2015-06-10 17:22 ` Ken Dreyer [this message]
2015-06-10 19:38 ` Robert LeBlanc
2015-06-18 13:44 ` Owen Synge
2015-06-18 20:35 ` Robert LeBlanc
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=55787270.10101@redhat.com \
--to=kdreyer@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=robert@leblancnet.us \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.