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

RFD: removing git.spec.in (Re: git 2.8.0 tarball rpmbuild error)

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 3, 2016, 03:41 UTC
Message-ID
<xmqqshz3fjeu.fsf_-_@gitster.mtv.corp.google.com>
In-Reply-To
<20160402161636.GD13271@zaya.teonanacatl.net>
It is likely that I'll cut 2.8.1 with only the attached patch
    Message-ID: <1459494651-32618-1-git-send-email-Matthieu.Moy@imag.fr>
    aka $gmane/290510

and I'll explicitly mark that this maintenance release is ignorable by people other than those who build their own RPM packages from my tree.

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.

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.

If a group of people feel strongly against the removal, they are welcome to form a volunteer group and promise to be responsible for regularly testing the tip of 'next' so that a breakage like this one will never slip to the 'master' branch.

Unless we see such a promise from dedicated group of people (whose size does not have to be more than 1), I think it is more harmful for us to pretend that we support RPM packaging out of our tree than being honest about it and removing the (pretense of) support.

Discuss.
Thanks.
-- >8 --
Subject: [PATCH] git.spec.in: use README.md, not README
From: Matthieu Moy <Matthieu.Moy@imag.fr>

The file was renamed in 4ad21f5 (README: use markdown syntax, 2016-02-25), but that commit forgot to update git.spec.in.

Reported-by: Ron Isaacson <isaacson.ljits@gmail.com>
Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>
---
 git.spec.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/git.spec.in b/git.spec.in
index d61d537..bfd1cfb 100644
--- a/git.spec.in
+++ b/git.spec.in
@@ -146,7 +146,7 @@ rm -rf $RPM_BUILD_ROOT
 %files -f bin-man-doc-files
 %defattr(-,root,root)
 %{_datadir}/git-core/
-%doc README COPYING Documentation/*.txt
+%doc README.md COPYING Documentation/*.txt
 %{!?_without_docs: %doc Documentation/*.html Documentation/howto}
 %{!?_without_docs: %doc Documentation/technical}
 %{_sysconfdir}/bash_completion.d
-- 
2.7.2.334.g35ed2ae.dirty
Previous: Todd ZullingerNext: Dennis Kaarsemaker
Message 4 of 7 in “git 2.8.0 tarball rpmbuild error”
  1. マッチョコ太郎Apr 2, 2016
  2. Pranit BauvaApr 2, 2016
  3. Todd ZullingerApr 2, 2016
  4. RFD: removing git.spec.in (Re: git 2.8.0 tarball rpmbuild error)Junio C Hamano, Apr 3, 2016
  5. Dennis KaarsemakerApr 4, 2016
  6. Makefile: stop pretending to support rpmbuildJunio C Hamano, Apr 5, 2016
  7. spec: Adjust README nameTodd Zullinger, Apr 2, 2016

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.