[EMAIL PROTECTED] wrote:
gozer 2004/08/06 19:52:08
static const command_rec modperl_cmds[] = {
MP_CMD_SRV_ITERATE("PerlSwitches", switches, "Perl Switches"),
-MP_CMD_SRV_ITERATE("PerlModule", modules, "PerlModule"),
-MP_CMD_SRV_ITERATE("PerlRequire", requires, "PerlRe
Philippe M. Chiasson wrote:
Stas Bekman wrote:
Philippe M. Chiasson wrote:
[...]
The question I have for all, is how can we make a directive support
.htaccess without
also allowing it in blocks. AFAIK, the httpd API only allows OR_ALL
for this and
it's both .htaccess and blocks.
How was this do
Philippe M. Chiasson wrote:
Is that a new directive? I thought you could use Perl only inside <>
It was introduced as a backend for sections and it's an available
artifact ;-)
Perl 'any valid perl code'
Can be put in the config file, as a single line ;-)
Neat, I didn't know that >> docs?
probably
Stas Bekman wrote:
Philippe M. Chiasson wrote:
I am looking at pending issues in todo/release, and I came upon this
issue
Right now, PerlModule PerlRequire can _only_ be used in Global
configuration and server scope. No , htacceess, etc.
The orignial conversation about this is here :
http://marc
Philippe M. Chiasson wrote:
what's 'Perl 1'?
The shortest way I can think of kicking an early interpreter startup in
httpd.conf ;-)
Is that a new directive? I thought you could use Perl only inside <>
Anybody disagrees strongly ?
Otherwise +1
Cool, so expect the todo entry to transform to a doc
Stas Bekman wrote:
Philippe M. Chiasson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you look in todo/release, you'll find this entry :
* sections:
~ A few issues with sections:
~
http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=106074969831522&w=2
~ owner: gozer
The strictness i
On Aug 6, 2004, at 4:39 PM, Stas Bekman wrote:
Please commit any tweaks directly...
Just did, thanks.
Regards,
David
smime.p7s
Description: S/MIME cryptographic signature
David Wheeler wrote:
On Aug 6, 2004, at 4:27 PM, Stas Bekman wrote:
Yes, it's a confusing explanation. How about this rewrite:
Much better. Thanks for the confirmation. Just a few nits:
Please commit any tweaks directly...
modperl-docs/src/docs/1.0/guide/install.pod
Thanks.
--
On Aug 6, 2004, at 4:33 PM, Stas Bekman wrote:
Here is the latest version. Is that clear now? Feel free to commit any
fixes directly. Thanks.
Many thanks, Stas!
Regards,
David
smime.p7s
Description: S/MIME cryptographic signature
Philippe M. Chiasson wrote:
I am looking at pending issues in todo/release, and I came upon this issue
Right now, PerlModule PerlRequire can _only_ be used in Global
configuration and server scope. No , htacceess, etc.
The orignial conversation about this is here :
http://marc.theaimsgroup.com/?t=
On Aug 6, 2004, at 4:27 PM, Stas Bekman wrote:
Yes, it's a confusing explanation. How about this rewrite:
Much better. Thanks for the confirmation. Just a few nits:
First check which malloc Perl was built with, by running:
% perl -V:usemymalloc
If you get:
usemymalloc='n';
it means that Perl is
Philippe M. Chiasson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you look in todo/release, you'll find this entry :
* sections:
~ A few issues with sections:
~
http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=106074969831522&w=2
~ owner: gozer
The strictness issue has been dealt
Stas Bekman wrote:
Here is the latest version. Is that clear now? Feel free to commit any
fixes directly. Thanks.
=head2 When DSO can be Used
Perl versions prior to 5.6.0, built with C<-Dusemymalloc>, and
versions 5.6.0 and higher, built with C<-Dusemymalloc> and
C<-Dbincompat5005>, pollutes the
David Wheeler wrote:
On Aug 6, 2004, at 2:45 PM, Stas Bekman wrote:
You may want to check the archives, David. There was a lot of
discussion regarding this issue.
http://perl.apache.org/docs/1.0/guide/
install.html#When_DSO_can_be_Used
documents the state of the art of the most recent discussi
I am looking at pending issues in todo/release, and I came upon this issue
Right now, PerlModule PerlRequire can _only_ be used in Global
configuration and server scope. No , htacceess, etc.
The orignial conversation about this is here :
http://marc.theaimsgroup.com/?t=10537008871&r=1&w=2
I'd
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you look in todo/release, you'll find this entry :
* sections:
~ A few issues with sections:
~
http://marc.theaimsgroup.com/?l=apache-modperl-dev&m=106074969831522&w=2
~ owner: gozer
The strictness issue has been dealt with a while ago. The only
On Aug 6, 2004, at 2:45 PM, Stas Bekman wrote:
You may want to check the archives, David. There was a lot of
discussion regarding this issue.
http://perl.apache.org/docs/1.0/guide/
install.html#When_DSO_can_be_Used
documents the state of the art of the most recent discussion, I
believe. If
David Wheeler wrote:
On Aug 6, 2004, at 1:47 PM, Vivek Khera wrote:
I successfully use mod_perl as a DSO on FreeBSD with usemymalloc='y'.
However, I do get a massive memory leak upon graceful restart of
Apache. So I just stop/start it instead :-)
Ick.
Otherwise there are no problems with it what
On Aug 6, 2004, at 1:47 PM, Vivek Khera wrote:
I successfully use mod_perl as a DSO on FreeBSD with usemymalloc='y'.
However, I do get a massive memory leak upon graceful restart of
Apache. So I just stop/start it instead :-)
Ick.
Otherwise there are no problems with it whatsoever.
I can't commen
On Aug 6, 2004, at 4:41 PM, David Wheeler wrote:
Then I can use a DSO mod_perl 1 with Perl 5.6 and later as long as
Perl wasn't compiled with usemymalloc='y' _and_
bincompat5005='define', correct?
I successfully use mod_perl as a DSO on FreeBSD with usemymalloc='y'.
However, I do get a massive m
Hi All,
Quick question about running mod_perl 1 as a DSO. If I'm understanding
this FAQ correctly:
http://perl.apache.org/docs/1.0/guide/install.html#When_DSO_can_be_Used
Then I can use a DSO mod_perl 1 with Perl 5.6 and later as long as Perl
wasn't compiled with usemymalloc='y' _and_ bincom
Geoffrey Young wrote:
At the moment one can build Perl APR only by building mod_perl, so I
suppose apxs is fine for now.
ok. so it looks like the way to handle this is via the new APR_VERSION and
APU_VERSION queries. this is in apxs:
my $apr_version = get_vars("APR_VERSION");
$apr_version =~
> At the moment one can build Perl APR only by building mod_perl, so I
> suppose apxs is fine for now.
ok. so it looks like the way to handle this is via the new APR_VERSION and
APU_VERSION queries. this is in apxs:
my $apr_version = get_vars("APR_VERSION");
$apr_version =~ s/(\d+)\.(\d).(
Geoffrey Young <[EMAIL PROTECTED]> writes:
[...]
> I guess what I was thinking about was someone who didn't care about mod_perl
> or httpd at all. that is, suppose I'm a user that simply wants perl
> bindings to APR - theoretically I could download only the APR/APU source and
> then build only t
Geoffrey Young wrote:
The situation with APR is no different than say BerkeleyDB. You can't
have the perl glue compiled against one major version and expect it to
work in applications which are linked to another. Once httpd-2.2 comes
out, modperl-2 users that want to upgrade the new server must r
> The situation with APR is no different than say BerkeleyDB. You can't
> have the perl glue compiled against one major version and expect it to
> work in applications which are linked to another. Once httpd-2.2 comes
> out, modperl-2 users that want to upgrade the new server must recompile
> m
Geoffrey Young <[EMAIL PROTECTED]> writes:
> moving this particular thread to [EMAIL PROTECTED]
>
> > mod_perl-2 should be getting the ap[ru] config script's
> > name/location from httpd (ie apxs). Like apreq, modperl's
> > apr ABI is subordinate to httpd, so asking apxs for the name
> > of th
moving this particular thread to [EMAIL PROTECTED]
> mod_perl-2 should be getting the ap[ru] config script's
> name/location from httpd (ie apxs). Like apreq, modperl's
> apr ABI is subordinate to httpd, so asking apxs for the name
> of the ap[ru] script it used is IMO the safest solution.
is
28 matches
Mail list logo
