Date: Sun, 10 May 1998 09:27:42 +0200 (W. Europe Daylight Time)
From: Rasmus Lerdorf <rasmus@lerdorf.on.ca>
To: new-httpd@apache.org
Subject: Re: [PATCH] Reorder the elements in ap_add_version_componants
In-Reply-To: <3.0.3.32.19980509194553.008b9510@hyperreal.org>
Message-ID: <Pine.WNT.3.96.980510092306.144B-100000@lerdorf.businessnet.dk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: new-httpd-owner@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

> I'm not sure I follow - is it that, if we removed SERVER_SUBVERSION, you'd
> say "right, PHP users, if you are using 1.3.0, you *must* use PHP 3.01 (or
> whatever), because the API has changed"?  But if we leave it in, you would
> not force people to use the new PHP release, and thus to stay compatible
> with 1.3bX releases you'd use SERVER_SUBVERSION?  Sorry about all the
> triple negatives there... 
> 
> Fortunately it's not like we have a big legacy of modules which use this
> yet.  I don't know of anyone outside php and perl using SUBVERSION.  I'd
> like to steer any new module author towards the new system; but I think
> it's a good thing to allow current perl and php users to use older versions
> of their own modules, for testing purposes or whatever.  And here I thought
> we were doing you a favor by leaving it in :)
> 
> It doesn't look like the mod_jserv folks care about it yet.... 

Hrm..  Early in the morning for me here and this is a bit hard to parse.  

Basically what I am saying is that it is a pain for me to check the MMN
when I build my .module file.  I would like to not have to worry about it
and just keep defining SERVER_SUBVERSION in that file and have Apache be
smart enough to not add the subversion twice if I also call
ap_add_version_components().  That means that no matter which server
version people use it will work.

-Rasmus