httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: APACHE_RELEASE no longer always increasing?
Date Tue, 09 Jun 1998 20:29:15 GMT
Martin Kraemer wrote:
> 
> On Tue, Jun 09, 1998 at 01:22:14PM -0400, Jim Jagielski wrote:
> > Rodent of Unusual Size wrote:
> > > > Where: MM is Major Version number
> > > >        NN is Minor Version number
> > > >        FF is "fix level"
> > > >        R is whether it's beta or final release
> > > >        BB is beta level.
> > > > 
> > > > Thus, 1.3.1b2 would be: 010301002
> > > > and 1.3.4 would be:     010304100
> > I'm not sure either, but maybe it's time to do it anyway :)
> 
> That'll break if any module relies on the fact that
> major == APACHE_RELEASE/1000000.
> But as it is very improbable that anyone would ever do comparisons
> other than < <= == >= > chances are about zero that old code will break.
> 
> +1 , with the (optional) addition of some macros? :
>     APACHE_RELEASE_MAJOR    -> 1
>     APACHE_RELEASE_MINOR    -> 3
>     APACHE_RELEASE_BETA     -> 7  for 1.3b7, 0 for 1.3.0
>     APACHE_RELEASE_IS_BETA  -> 1  for 1.3b7, 0 for 1.3.0
> 

I'd prefer APACHE_RELEASE_IS_FINAL over _IS_BETA because we want
that "flag" to be 1 for finals and 0 for betas. Good Idea about
the macros! +1  (PS: Need APACHE_RELEASE_FIXLEVEL (or PATCHLEVEL?))

-- 
===========================================================================
   Jim Jagielski   |||   jim@jaguNET.com   |||   http://www.jaguNET.com/
            "That's no ordinary rabbit... that's the most foul,
            cruel and bad-tempered rodent you ever laid eyes on"

Mime
View raw message