On 02.03.2012 00:34, Sorin Manolache wrote:
On 03/02/12 00:21, Ben Noordhuis wrote:
On Thu, Mar 1, 2012 at 17:29,sorin.manola...@orange.com wrote:
Hello,
I would need a memory buffer associated per worker thread (in the worker
MPM) or to each process (in the prefork MPM).
In order to do
On Mar 2, 2012, at 2:50 PM, Stefan Fritsch wrote:
On Wednesday 29 February 2012, Jim Jagielski wrote:
On Feb 29, 2012, at 10:32 AM, William A. Rowe Jr. wrote:
It's the reason why mod_aspdotnet was ejected, and why mod_arm4,
mod_ftp and perhaps even mod_fcgid are all on their way out of
the
On Mar 2, 2012, at 1:28 PM, William A. Rowe Jr. wrote:
A proposal to adopt mod_policy is attached.
[X] Option 1: adopt as trunk module
[ ] Option 2: adopt only as subproject
[ ] Option 3: do not adopt
But it would have to be clear that inclusion into trunk would not by
default mean that they would be included in the next major release.
Especially for mod_ftp, I think that it requires many more eyeballs
and a comprehensive test suite before it should be part of a stable
release.
A proposal to adopt mod_combine is attached.
[ ] Option 1: adopt as trunk module
[ ] Option 2: adopt only as subproject
[ ] Option 3: do not adopt
[Prior to this vote, this proposal had not passed; jim alone had joined
minfrin in supporting the proposal. Please take another look and
On 02.03.2012 11:44, Michael Felt wrote:
Well, as long as I dont need a compiler (as I dont have one installed
here, dont want test to be dependent on compiler, or dev related files
not normally found on production system) this wont be a problem - I will
just install the packages and then
thx
On Sat, Mar 3, 2012 at 7:42 PM, Rainer Jung rainer.j...@kippdata.de wrote:
On 02.03.2012 11:44, Michael Felt wrote:
Well, as long as I dont need a compiler (as I dont have one installed
here, dont want test to be dependent on compiler, or dev related files
not normally found on
On 03.03.2012 15:22, Eric Covener wrote:
But it would have to be clear that inclusion into trunk would not by
default mean that they would be included in the next major release.
Especially for mod_ftp, I think that it requires many more eyeballs
and a comprehensive test suite before it should
On 01.03.2012 19:11, William A. Rowe Jr. wrote:
Let's simply reset this whole mess.
A proposal to adopt mod_firehose is attached.
[X] Option 1: adopt as trunk module
[ ] Option 2: adopt only as subproject
[ ] Option 3: do not adopt
Option 1.
Regards,
Rainer
On 02.03.2012 19:28, William A. Rowe Jr. wrote:
A proposal to adopt mod_policy is attached.
[X] Option 1: adopt as trunk module
[ ] Option 2: adopt only as subproject
[ ] Option 3: do not adopt
+1 for Option 1.
Regards,
Rainer
Hey folks,
or rather: Jeff :)
I'm finally getting around to updating my stack to httpd 2.4.1
(and PHP 5.4) and some things are breaking.
mod_whatkilledus doesn't build with 2.4.1:
/opt/bw/share/apr/build/libtool --silent --mode=compile gcc -std=gnu99
-prefer-pic -march=corei7 -maes -O3 -g
Am 04.03.2012 02:35, schrieb Igor Galić:
Hey folks,
or rather: Jeff :)
I'm finally getting around to updating my stack to httpd 2.4.1
(and PHP 5.4) and some things are breaking.
mod_whatkilledus doesn't build with 2.4.1
you are aware that PHP 5.4.0 currently does not support Apache 2.4?
On Sat, Mar 3, 2012 at 8:35 PM, Igor Galić i.ga...@brainsware.org wrote:
Hey folks,
or rather: Jeff :)
try again :)
I'm finally getting around to updating my stack to httpd 2.4.1
(and PHP 5.4) and some things are breaking.
mod_whatkilledus doesn't build with 2.4.1:
[snip]
You will need to rebuild all external modules of course given its a
new major (like php, mod_perl etc)
The latest stable of mod_perl (2.0.5) doesn't currently build with
2.4.1. Haven't checked out the trunk.
i
--
Igor Galić
Tel: +43 (0) 664 886 22 883
Mail: i.ga...@brainsware.org
Assuming you mean mod_php - I'm sure that php with FastCGI works
fine... Like any fresh software release, it can be expected that not
every 3rd party module developer has gotten around to upgrading their
code. Give it a bit of time; it'll happen.
On 04/03/2012 03:53, Reindl Harald wrote:
Am
After going through the thread in question, I disagree with your
statement. The PHP dev team did a wonderful job in deciding to promote
a patch against the shiny new PHP 5.4.0 that should work with httpd
2.4, they're trying to roadmap the patch in to the next release, and
they're probably right
16 matches
Mail list logo
