bloody challenging MakeMaker methods overriding

2003-03-20 Thread Stas Bekman
I'm splitting my hair for a few days trying to figure out how to figure out whether it was ExtUtils::MakeMaker who has overriden some MY::foo method or Makefile.PL. The thing is, when Makefile.PL is invoked recursively, it moves all the MY:: overriden methods into some other package and replace

Re: (mp2) Apache::Build

2003-03-20 Thread Stas Bekman
Kermit Tensmeyer wrote: [...] '/usr/local/apache/bin/apxs'; as nears as I can tell, the last option is a hard-code hack that will fail for most sites Sorry if I've snipped too much, but am I correct that this is the gist of the problem? mp2's build picks the wrong /usr/local/apache/bi

AIX: ld -bI:httpd.exp vs. ld -lhttpd

2003-03-20 Thread Stas Bekman
In mod_perl 2.0 on AIX we have to import symbols from ap_ and apr_ namespaces when linking the shared object (the other approach is to use -berok which works as symbols get resolved at load time, but this is too error-prone). The following two ways to import apr_ symbols seem to have the same ef

(mp2) Apache::Build

2003-03-20 Thread Kermit Tensmeyer
I did a grep on the use of apxs in the modperl pm files and found that it is used to extract 4 different variables (includedir, prefix, cflags, libexecdir). if $build->apxs (Apache::Build::apxs) was not used, the same functionality could be achieved that storing those values in the $build hash. T

Re: [patch] ($r|$s)->is_hook_enabled($hook_name)

2003-03-20 Thread Stas Bekman
Geoffrey Young wrote: I think we should go with get_config first of all, so we have the Apache like functionality and later on we can provide a shortcut with syntax sugar. So we start with: my $dir_cfg = $self->get_config($s, $r->per_dir_config); my $srv_cfg = $self->get_config($s); And then we

Re: [patch] ($r|$s)->is_hook_enabled($hook_name)

2003-03-20 Thread Geoffrey Young
I think we should go with get_config first of all, so we have the Apache like functionality and later on we can provide a shortcut with syntax sugar. So we start with: my $dir_cfg = $self->get_config($s, $r->per_dir_config); my $srv_cfg = $self->get_config($s); And then we can have something lik

Re: [patch] ($r|$s)->is_hook_enabled($hook_name)

2003-03-20 Thread Stas Bekman
Geoffrey Young wrote: So first of all I've called the method: is_hook_enabled and it checks srv config flags when called as $s->is_hook_enabled($hook_name) or dir config flags if called as $r->is_hook_enabled($hook_name). Is that a healthy API? Or should we use: my $dir_cfg = $self->get_co

Re: [patch] ($r|$s)->is_hook_enabled($hook_name)

2003-03-20 Thread Geoffrey Young
So first of all I've called the method: is_hook_enabled and it checks srv config flags when called as $s->is_hook_enabled($hook_name) or dir config flags if called as $r->is_hook_enabled($hook_name). Is that a healthy API? Or should we use: my $dir_cfg = $self->get_config($s, $r->per_dir_c