Return-Path: Delivered-To: apmail-perl-dev-archive@perl.apache.org Received: (qmail 11242 invoked by uid 500); 14 May 2003 23:03:02 -0000 Mailing-List: contact dev-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@perl.apache.org Received: (qmail 11128 invoked from network); 14 May 2003 23:03:01 -0000 Received: from erato.logilune.com (HELO mail.logilune.com) (195.154.174.52) by daedalus.apache.org with SMTP; 14 May 2003 23:03:01 -0000 Received: from stason.org (localhost.logilune.com [127.0.0.1]) by mail.logilune.com (Postfix) with ESMTP id 75D4A79791; Thu, 15 May 2003 01:03:06 +0200 (CEST) Message-ID: <3EC2CB24.4020606@stason.org> Date: Thu, 15 May 2003 09:03:00 +1000 From: Stas Bekman Organization: Hope, Humanized User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Geoffrey Young Cc: dev@perl.apache.org Subject: Re: apache 2.0 vs 2.1 References: <3EC27A89.6000608@modperlcookbook.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Geoffrey Young wrote: > is there some generic way we want to think about integrating changes > between apache 2.0 and 2.1? > > what is particularly piquing my interest (today) is the aaa stuff. I > wrote a patch that added the different AUTH_* constants to > Apache::Const, but it clearly needs to be separated out somehow since > mod_auth.h doesn't exist in 2.0. same with ap_register_provider and > some other functions that are useful for hooking into the new aaa scheme. > > so, what do we do? not support 2.1 yet? write in a bunch of ifdefs > surrounding the new routines? create new routines in the generation > thingies that recognize the MMN and do the right thing? We can't really support 2.1. If I understand correctly all features committed to 2.1 are experemental and can be removed at any moment. Currently if you want to add a new feature to 2.x you go and commit it to the 2.1 (HEAD) trunk. Then people vote if this feature is good/wanted and then it gets backported to 2.0. If you want a particular feature to be in 2.0 you have to advocate httpd commiters to vote 3 +1 (and no -1s) and then it'll go into 2.0 and then we can support it. You may want to run this through httpd-dev, just in case that my understanding of their approach is wrong. I thought that aaa was already in 2.0. Isn't that the case? __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:stas@stason.org http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@perl.apache.org For additional commands, e-mail: dev-help@perl.apache.org