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

Re: [PATCH] rpmbuild doesn't like '-' in version strings

From
Junio C Hamano <junkio@cox.net>
Date
Jan 14, 2006, 19:17 UTC
Message-ID
<7v1wzaliv0.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<43C91B25.9030707@research.att.com>
John Ellson <ellson@research.att.com> writes:
Show 5 quoted lines
>> ...  In that
>> sense, maybe leaving the interim version unbuildable for binary
>> packaging might be considered a feature.
>
> What happened to this?

I consider leaving the interim version unbuildable for binary packaging consider a feature.

If you want to build your own version, I think you could locally tag that head and build, like:

	$ git tag -a "John's GIT 1.1.2+frotz patch" v1.1.2.John0114
	$ make rpmbuild

Of course you can keep a patch with the sed -e 's/-/_/' in GIT-VERSION-GEN as Linus suggested in your development branch. I am not yet convinced being able to build a random unidentifiable binary package is a good thing, and "the number of minutes/seconds monotonicity" would not work in multiple branches case (i.e. still leaves the result unordered).

Previous: Linus TorvaldsNext: John Ellson
Message 8 of 11 in “rpmbuild doesn't like '-' in version strings”
  1. rpmbuild doesn't like '-' in version stringsJohn Ellson, Dec 30, 2005
  2. Junio C HamanoJan 6, 2006
  3. Andreas EricssonJan 7, 2006
  4. Johannes SchindelinJan 7, 2006
  5. Ryan AndersonJan 7, 2006
  6. John EllsonJan 14, 2006
  7. Linus TorvaldsJan 14, 2006
  8. Junio C HamanoJan 14, 2006
  9. John EllsonJan 14, 2006
  10. Junio C HamanoJan 14, 2006
  11. Junio C HamanoJan 16, 2006

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.