This is the mail archive of the newlib@sourceware.org mailing list for the newlib 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: RFC: Version information string vs. version number

From: Ralf Corsepius <ralf dot corsepius at rtems dot org>
To: Ole Reinhardt <ole dot reinhardt at thermotemp dot de>
Cc: newlib at sourceware dot org
Date: Mon, 16 Feb 2009 19:12:28 +0100
Subject: Re: RFC: Version information string vs. version number
References: <1234780179.7199.25.camel@localhost> <c46d4d430902160437gd511df3i9758e6a950954c28@mail.gmail.com> <1234807085.7199.47.camel@localhost>

Ole Reinhardt wrote:

Hi,

This won't work well for newlib, because the release discipline
amounts to "update the version every december". You'ld need to use the
CVS revision number. There is no correlation between the nominal
newlib version number and the feature set.


Oh, I understand. Is there any other way to differentiate between those
versions / feature sets?

Don't rely on versions, but check for them. One way to do so would be using autoconf.

Ralf

References:
- RFC: Version information string vs. version number
  - From: Ole Reinhardt
- Re: RFC: Version information string vs. version number
  - From: Ole Reinhardt

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