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,
William McKee wrote:
On Fri, Dec 31, 2004 at 02:02:59PM -0500, Stas Bekman wrote:
Thanks William, I've committed that with a few tweaks. Especially the last
para. Please check that it still makes sense.
Looks fine except for a couple of typos (dangling quote mark and
mispelled 'should'). Also, no
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
On Fri, Dec 31, 2004 at 02:02:59PM -0500, Stas Bekman wrote:
> Thanks William, I've committed that with a few tweaks. Especially the last
> para. Please check that it still makes sense.
Looks fine except for a couple of typos (dangling quote mark and
mispelled 'should'). Also, now that I'm a bit
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,
William McKee wrote:
Thanks for the clear explanation of *.a and *.so files, Stas. I'm
starting to grok how it works together.
I've attached the diff to the install docs to this message which
incorporates some of your notes about .so and .a files. I found this
information hard to find while browsin
On Fri, 31 Dec 2004, Stas Bekman wrote:
> Octavian Rasnita wrote:
> > Hi,
> >
> > I want to configure a production server that uses
> > mod_perl and I don't know what version to choose because
> > I see that mod_perl 2 is not stable yet. What do you
> > recommend, to install Apache 1.3 and mod_per
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
I know what's happening now, it dawned on me after I wrote this last night.
A deadlock happens when you have an updater that acquires a write
lock, but it's waiting for the first updater that is also in a SELECT
FOR UPDATE but has not yet acquired a write lock. The first updater
can't finish be
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
Thanks for the clear explanation of *.a and *.so files, Stas. I'm
starting to grok how it works together.
I've attached the diff to the install docs to this message which
incorporates some of your notes about .so and .a files. I found this
information hard to find while browsing Google, Perlmonks
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
William McKee wrote:
On Thu, Dec 30, 2004 at 05:57:07PM -0500, Stas Bekman wrote:
During compilation of mod_perl, I was seeing undefined reference errors
which are nicely described on the install page[1]. The prescription
suggests rebuilding Perl with dynamic linking; apparently the version
that's
Octavian Rasnita wrote:
Hi,
I want to configure a production server that uses mod_perl and I don't know
what version to choose because I see that mod_perl 2 is not stable yet.
What do you recommend, to install Apache 1.3 and mod_perl 1 and use it until
mod_perl 2 will be stable enough, or do you th
Joshua Hoblitt wrote:
On Mon, Dec 27, 2004 at 12:10:47PM -0500, Perrin Harkins wrote:
The real significant issue to address, IMO, has to do with CPAN's
indexing of the Apache:: modules common to both mp1 and mp2 core
distros, because those packages set the underlying apache[12]
architecture.
That'
On Thu, Dec 30, 2004 at 05:57:07PM -0500, Stas Bekman wrote:
> >During compilation of mod_perl, I was seeing undefined reference errors
> >which are nicely described on the install page[1]. The prescription
> >suggests rebuilding Perl with dynamic linking; apparently the version
> >that's shipped w
On Mon, Dec 27, 2004 at 12:10:47PM -0500, Perrin Harkins wrote:
> > The real significant issue to address, IMO, has to do with CPAN's
> > indexing of the Apache:: modules common to both mp1 and mp2 core
> > distros, because those packages set the underlying apache[12]
> > architecture.
>
> That's
26 matches
Mail list logo
