From: Dennis Kaarsemaker <dennis@kaarsemaker•net>
To: Junio C Hamano <gitster@pobox•com>,
git@vger•kernel.org, Matthieu Moy <Matthieu.Moy@imag•fr>
Cc: "Todd Zullinger" <tmz@pobox•com>,
"Pranit Bauva" <pranit.bauva@gmail•com>,
マッチョコ太郎 <mebius1080p@gmail•com>
Subject: Re: RFD: removing git.spec.in (Re: git 2.8.0 tarball rpmbuild error)
Date: Mon, 04 Apr 2016 20:20:01 +0200 [thread overview]
Message-ID: <1459794001.19561.10.camel@kaarsemaker.net> (raw)
In-Reply-To: <xmqqshz3fjeu.fsf_-_@gitster.mtv.corp.google.com>
On za, 2016-04-02 at 20:41 -0700, Junio C Hamano wrote:
> I think by now it is very clear that nobody active in the Git
> development community tests RPM binaries built with git.spec.in we
> have in our tree. I suspect RPM based distros are using their own
> RPM build recipe without paying any attention to what we have in our
> tree, and that is why no packager from RPM land gave any bug report
> and correction before the release happened.
Fedora, RHEL, CentOS, OpenSUSE and Mageia all use their own specfiles
and local patches. I do test and distribute RPM packages based on the
next branch, but use fedora's packaging to do so (which incidentally
also broke and I had to work around this change, but I completely
forgot about git.spec.in).
> I'd propose that during the cycle for the next feature release, we'd
> remove git.spec.in and stop pretending as if we support RPM
> packaging.
I would be in favor of that. In general, I find it much better to use a
distro's packaging and simply transplanting a tarball into it. That
keeps the difference with what the distro provides minimal.
--
Dennis Kaarsemaker
www.kaarsemaker.net
next prev parent reply other threads:[~2016-04-04 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-02 15:48 git 2.8.0 tarball rpmbuild error マッチョコ太郎
2016-04-02 16:01 ` Pranit Bauva
2016-04-02 16:16 ` Todd Zullinger
2016-04-03 3:41 ` RFD: removing git.spec.in (Re: git 2.8.0 tarball rpmbuild error) Junio C Hamano
2016-04-04 18:20 ` Dennis Kaarsemaker [this message]
2016-04-05 6:51 ` [PATCH] Makefile: stop pretending to support rpmbuild Junio C Hamano
2016-04-02 16:14 ` [PATCH] spec: Adjust README name Todd Zullinger
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=1459794001.19561.10.camel@kaarsemaker.net \
--to=dennis@kaarsemaker$(echo .)net \
--cc=Matthieu.Moy@imag$(echo .)fr \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=mebius1080p@gmail$(echo .)com \
--cc=pranit.bauva@gmail$(echo .)com \
--cc=tmz@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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