This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PATCH: Bump version on mainline


Zack Weinberg wrote:
"Joseph S. Myers" <joseph@codesourcery.com> writes:


If the number of locations of the version number are to be reduced
further, either the unique location should be gcc-common.texi or
update_web_docs needs to be updated to generate whatever generated
.texi file gets the version number when building online docs.


I have had the following idea for version numbers floating around in
my head for some time now.  It attempts to address the following
problems:

Funny, I was going to suggest something very similar.


However, I would also like to add something like --with-distributor and --with-support-url. So that, for example, we could build GCC 3.4.2 without modifying the sources at all, but with appropriate configuration options, and get:

3.4.2 (CodeSourcery 2005Q1A)

That's a superset of your improvement, though.

Your improvement would also be nice in that it would allow us to easily automate one more step of the release process. Right now, you're supposed to remote the datestamp just long enough to create the final tarball; no reason the release script couldn't just make DATESTAMP a zero-length file instead, without actually mucking with CVS.

Would you like to implement your suggestion? I can't imagine anyone objecting to your idea, though my configure options might be a little more controversial.

--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
(916) 791-8304


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]