From: Junio C Hamano <gitster@pobox.com>
To: Todd Zullinger <tmz@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Erez Zilber <erezzi.list@gmail.com>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Running "make rpm" fails on a CentOS 6.3 machine
Date: Mon, 03 Feb 2014 10:08:04 -0800 [thread overview]
Message-ID: <xmqqmwi8f4sb.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140130185104.GV3241@zaya.teonanacatl.net> (Todd Zullinger's message of "Thu, 30 Jan 2014 13:51:04 -0500")
Todd Zullinger <tmz@pobox.com> writes:
> I know the Fedora/EPEL spec file and what's in git.git have grown
> apart a good bit, unfortunately. That's the cost of having a spec
> file that is meant to work across a very wide array of RPM-based
> systems, I guess. The Fedora/EPEL spec file is fairly specific to the
> Fedora/EPEL build tools (mock is the primary build tool).
Hmph.
Once it gets to the point where our "spec" file is so out of sync
with anybody's RPM based distribution in the real world, I suspect
that removing and not shipping it in tree might be more helpful to
the users. Or at least have a set of pointers, one for each major
RPM based distribution, where to obtain spec file more tailored for
their platform, at the beginning of it, or something.
Have we already reached that point? Does anybody still use it?
prev parent reply other threads:[~2014-02-03 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 10:29 Running "make rpm" fails on a CentOS 6.3 machine Erez Zilber
2014-01-30 8:05 ` Erez Zilber
2014-01-30 18:16 ` Jonathan Nieder
2014-01-30 18:51 ` Todd Zullinger
2014-02-02 20:38 ` Erez Zilber
2014-02-02 21:07 ` Todd Zullinger
2014-02-03 11:10 ` Erez Zilber
2014-02-03 14:24 ` Todd Zullinger
2014-02-03 15:16 ` Martin Langhoff
2014-02-03 15:21 ` Todd Zullinger
2014-02-03 18:08 ` 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=xmqqmwi8f4sb.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=erezzi.list@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=tmz@pobox.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