> I would like to support Randal's contention (if not his tone) that
> indeed, in real-world mod_perl commercial situations that I'm familiar
> with (say about 8), 80% of those real-world users will want to have both
> mod_perl 1 and mod_perl 2 installed concurrently due to the
> generally-accepted
> Stas> 99.9% of users do *not* need to use this workaround. So that
> Stas> issue is moot if you ask me.
> Four out of my five biggest customers *will* need to have both
> modperl1 and modperl2 in the same Perl installation tree on their
> development machines, because they'll need to start looki
On Wed, 5 Jan 2005, Frank Wiles wrote:
> Date: Wed, 5 Jan 2005 10:21:01 -0600
> From: Frank Wiles <[EMAIL PROTECTED]>
> To: Geoffrey Young <[EMAIL PROTECTED]>
> Cc: modperl@perl.apache.org
> Subject: Re: [summary] The Conflict of mp1 vs mp2 vs mp22 vs ... vs mpNN
&g
On Wed, 05 Jan 2005 10:50:39 -0500
Geoffrey Young <[EMAIL PROTECTED]> wrote:
>
> > Admit it, Stas, The wheels have fallen off you nasty hack re
> > namespaces.
> > Stop trying to defend the indefensible.
> >
> > Just fix it!
>
> this kind of barb is really counterproductive, as have been many,
> Admit it, Stas, The wheels have fallen off you nasty hack re namespaces.
> Stop trying to defend the indefensible.
>
> Just fix it!
this kind of barb is really counterproductive, as have been many, many of
the remarks directed at Stas over the past two weeks. I can't imagine how
anyone would
Hi Folks
It gets worse :-(.
Apache::Test can't be upgraded...
Server Version: Apache/2.0.50 (Win32) mod_perl/1.99_15-dev Perl/v5.8.4
Apache::Test V 1.13 installed in the sane directory
/perl/site/lib/Apache/
Apache::Build V 0.01 installed in the pathological directory
/perl/site/lib/Apache2/Apac
At 4:40 PM -0500 12/31/04, Stas Bekman wrote:
It's unheard of that an open source project will be prevented from
being released, because the infrastructure doesn't support it. And
because a few folks suddenly decided to wear god caps.
But in your summary you point out that PAUSE will happily hand
On Sat, 1 Jan 2005, Render Web wrote:
[ ... ]
> p.s.
> Under windows (perl 5.6 for MP1 and 5.8.x for MP2) forcing
> distinct perl installs.
Just a minor clarification on this, for the archives - while
it's true that perl-5.8.x is required for mp2 on Win32, mp1
can run now on either 5.6.x or 5.8
Stas> 99.9% of users do *not* need to use this workaround. So that
Stas> issue is moot if you ask me.
Randal> You keep saying this like you believe it. In fact, the number
keeps
Randal> getting closer to 100% each time.
Randal> This is pure, fabricated *fiction*.
For me, this ends up being the s
Randal L. Schwartz wrote:
Four out of my five biggest customers *will* need to have both
modperl1 and modperl2 in the same Perl installation tree on their
Bullcrap - I would say that sep perl installs is not enough!
Personally I would hate to work for anyone who does insists
on dev/testing on live
John Siracusa wrote:
On 12/31/04 4:40 PM, Stas Bekman wrote:
Finally you don't want to use it - don't use it. It's an open source
software, it will succeed or fail by *its own merits* and not because the
infrastructure has a long known problem but is not willing to evolve.
And to repeat this again.
> "Stas" == Stas Bekman <[EMAIL PROTECTED]> writes:
Stas> 99.9% of users do *not* need to use this workaround. So that
Stas> issue is moot if you ask me.
You keep saying this like you believe it. In fact, the number keeps
getting closer to 100% each time.
This is pure, fabricated *fiction*.
On 12/31/04 4:40 PM, Stas Bekman wrote:
> Finally you don't want to use it - don't use it. It's an open source
> software, it will succeed or fail by *its own merits* and not because the
> infrastructure has a long known problem but is not willing to evolve.
>
> And to repeat this again. If you ins
Adam Kennedy wrote:
[...]
[my apologies if I've over-trimmed Adams original, but it's hard to keep
focused on such a huge email]
Why mod_perl2 didn't Rename its API
The reason for not renaming mp2 core and 3rd party modules APIs
to embed the version number like (mod_perl2, Apache2::Cookie,
Apache
I'm going to chime in, as someone working on a suite of modules that are
intended to eventually work with apache 1.x and 2.x. First, I agree with
this:
On 12/31/04 2:27 PM, Adam Kennedy wrote:
> For the moment, I'm asking just that the release of mod_perl 2.0 be put
> on hold until this problem,
Joe Schaefer wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
Randy Kobes wrote:
[...]
There's still mod_perl.pm in both packages, though. In mp2,
this is just something to define the version, and also to
provide a NAME pod section (if I remember correctly, this
was inserted for the benefit of sea
Stas Bekman <[EMAIL PROTECTED]> writes:
> Randy Kobes wrote:
[...]
>> There's still mod_perl.pm in both packages, though. In mp2,
>> this is just something to define the version, and also to
>> provide a NAME pod section (if I remember correctly, this
>> was inserted for the benefit of search.cp
Randy Kobes wrote:
Stas, that was a a very useful summary of the issues -
thanks for putting that together!
:)
On Fri, 31 Dec 2004, Stas Bekman wrote:
Joe Schaefer wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
Joe Schaefer wrote:
[...]
I now think was a mistake for any of the Apache::* core modu
Stas, that was a a very useful summary of the issues -
thanks for putting that together!
On Fri, 31 Dec 2004, Stas Bekman wrote:
> Joe Schaefer wrote:
> > Stas Bekman <[EMAIL PROTECTED]> writes:
> >
> >>Joe Schaefer wrote:
> > [...]
> > I now think was a mistake for any of the Apache::* core mod
(This email will also be posted to http://ali.as/devel/mod_perl2.html
for future reading.)
If I haven't addressed something in my summary please let me know
in that thread on the modperl users list (let's not spread it
over multiple lists). Thank you.
Responding here as requested. Before I begin,
Joe Schaefer wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
Joe Schaefer wrote:
[...]
Looks very promising to me. Is there a way to tell PAUSE to index
mod_perl's Apache::* modules from a bundle? If so, that might
provide a decent solution for both mod_perl and libapreq
(and other Apache::* mo
Stas Bekman <[EMAIL PROTECTED]> writes:
> Joe Schaefer wrote:
[...]
>> Looks very promising to me. Is there a way to tell PAUSE to index
>> mod_perl's Apache::* modules from a bundle? If so, that might
>> provide a decent solution for both mod_perl and libapreq
>> (and other Apache::* modules
Joe Schaefer wrote:
Stas Bekman <[EMAIL PROTECTED]> writes:
[...]
--
Meanwhile I've found a solution proposed by Andreas 1.5 years ago, which
might work as a better workaround from all the ones proposed so far:
http://www.xray.mpe.mp
Stas Bekman <[EMAIL PROTECTED]> writes:
[...]
> --
> Meanwhile I've found a solution proposed by Andreas 1.5 years ago, which
> might work as a better workaround from all the ones proposed so far:
> http://www.xray.mpe.mpg.de/mailin
24 matches
Mail list logo
