Hi, > > i'd rather not add this, simply because i'd like to see as few build > options as possible in 2.0. the pile of build options in 1.x has led to a > great deal of confusion and mess. you should instead use the > MP_INST_APACHE2=1 option, then you can use the modperl-2.0/blib with > PerlModule Apache2 configured. >
I don't use this option, because it's not the default and I want to test the default case (at least for the moment) and when I last tried it (ok, this was long ago) it didn't work, because it is not the default and it seems that at this time nobody had used it. Maybe I should retry it.... > also thinking about making MP_INST_APACHE2 the default. any thoughts on > that? > >From my expericence with the step from Embperl 1.x to Embperl 2.x I would say: yes make it the default. Since mod_perl 2 isn't (and can't) be 100% compatible with 1.x, it is not a drop in replacement and if you have a set of applications that are running fine with 1.x, there is no need to rewrite (normaly you won't have the time, to adapt them to 2.x), but for new application you may want to use 2.x. The backdraw is that modules that tries to run with both versions, need some extra logic, but they will need it anyway, since this option exists and poeple will use it. I think we need a smooth upgrade path, nobody will switch in one day. So +1 for making it the default. (maybe even going one step further, makeing it the default and removing the option to change it) Gerald ------------------------------------------------------------- Gerald Richter ecos electronic communication services gmbh Internetconnect * Webserver/-design/-datenbanken * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131 WWW: http://www.ecos.de Fax: +49 6133 925152 ------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
