Hi all,
It looks like we've reached a consensus on this, so absent any objections,
I went ahead and moved this to the voting phase.
If you're eligible to vote on RFC's, please navigate to the RFC and cast
your vote now:
https://wiki.php.net/rfc/apxs-loadmodule
In case you weren't following the previous thread, this is a very
low-impact RFC that will add a new, optional switch to the configure
script. This switch, if specified, would tell APXS (which already has this
functionality built-in) not to write the LoadModule line to httpd.conf when
"make install" is performed. This is a feature that has been requested for
some time and would allow people with manually-built PHP installs to
isolate their mod_php hooks in a separate php.conf file without having to
manually edit httpd.conf whenever a new build is performed.
If this optional switch is not specified, the configure script will behave
exactly as it does now. As such, this RFC will not alter configure's
existing behavior unless you explicitly include this new switch.
Please let me know if you have any last-minute questions. Otherwise, happy
voting! Thanks!
--Kris
Just a friendly reminder to vote on this if you haven't already. 5 people
have voted on it thus far but I'd like to have at least twice that by the
time voting closes.
You can read the RFC and vote on it at:
https://wiki.php.net/rfc/apxs-loadmodule
Thanks!
--Kris
Hi all,
It looks like we've reached a consensus on this, so absent any objections,
I went ahead and moved this to the voting phase.If you're eligible to vote on RFC's, please navigate to the RFC and cast
your vote now:https://wiki.php.net/rfc/apxs-loadmodule
In case you weren't following the previous thread, this is a very
low-impact RFC that will add a new, optional switch to the configure
script. This switch, if specified, would tell APXS (which already has this
functionality built-in) not to write the LoadModule line to httpd.conf when
"make install" is performed. This is a feature that has been requested for
some time and would allow people with manually-built PHP installs to
isolate their mod_php hooks in a separate php.conf file without having to
manually edit httpd.conf whenever a new build is performed.If this optional switch is not specified, the configure script will behave
exactly as it does now. As such, this RFC will not alter configure's
existing behavior unless you explicitly include this new switch.Please let me know if you have any last-minute questions. Otherwise,
happy voting! Thanks!--Kris
FYI-
Voting will be closed at 2 PM (PST) tomorrow.
--Kris
Just a friendly reminder to vote on this if you haven't already. 5 people
have voted on it thus far but I'd like to have at least twice that by the
time voting closes.You can read the RFC and vote on it at:
https://wiki.php.net/rfc/apxs-loadmoduleThanks!
--Kris
Hi all,
It looks like we've reached a consensus on this, so absent any
objections, I went ahead and moved this to the voting phase.If you're eligible to vote on RFC's, please navigate to the RFC and cast
your vote now:https://wiki.php.net/rfc/apxs-loadmodule
In case you weren't following the previous thread, this is a very
low-impact RFC that will add a new, optional switch to the configure
script. This switch, if specified, would tell APXS (which already has this
functionality built-in) not to write the LoadModule line to httpd.conf when
"make install" is performed. This is a feature that has been requested for
some time and would allow people with manually-built PHP installs to
isolate their mod_php hooks in a separate php.conf file without having to
manually edit httpd.conf whenever a new build is performed.If this optional switch is not specified, the configure script will
behave exactly as it does now. As such, this RFC will not alter
configure's existing behavior unless you explicitly include this new switch.Please let me know if you have any last-minute questions. Otherwise,
happy voting! Thanks!--Kris
Voting is now closed. This RFC was passed unanimously 12-0.
I'll commit the changes to 5.4 at the earliest opportunity. I just
realized that the language was somewhat vague as to whether it should be
applied to 5.3 branch or not; I don't really care either way but I'll
probably just go ahead and apply it to both unless anyone has any
objections.
Thanks!
--Kris
FYI-
Voting will be closed at 2 PM (PST) tomorrow.
--Kris
Just a friendly reminder to vote on this if you haven't already. 5
people have voted on it thus far but I'd like to have at least twice that
by the time voting closes.You can read the RFC and vote on it at:
https://wiki.php.net/rfc/apxs-loadmoduleThanks!
--Kris
On Tue, Feb 28, 2012 at 12:19 PM, Kris Craig kris.craig@gmail.comwrote:
Hi all,
It looks like we've reached a consensus on this, so absent any
objections, I went ahead and moved this to the voting phase.If you're eligible to vote on RFC's, please navigate to the RFC and cast
your vote now:https://wiki.php.net/rfc/apxs-loadmodule
In case you weren't following the previous thread, this is a very
low-impact RFC that will add a new, optional switch to the configure
script. This switch, if specified, would tell APXS (which already has this
functionality built-in) not to write the LoadModule line to httpd.conf when
"make install" is performed. This is a feature that has been requested for
some time and would allow people with manually-built PHP installs to
isolate their mod_php hooks in a separate php.conf file without having to
manually edit httpd.conf whenever a new build is performed.If this optional switch is not specified, the configure script will
behave exactly as it does now. As such, this RFC will not alter
configure's existing behavior unless you explicitly include this new switch.Please let me know if you have any last-minute questions. Otherwise,
happy voting! Thanks!--Kris
Kris Craig wrote:
I'll commit the changes to 5.4 at the earliest opportunity. I just
realized that the language was somewhat vague as to whether it should be
applied to 5.3 branch or not; I don't really care either way but I'll
probably just go ahead and apply it to both unless anyone has any
objections.
Any reason to change the 'logic' of 5.3 now? Having already been hit by a 5.4
change that has not been back-ported, some consistency on what is and isn't
would be helpful, and I don't think there is any point changing this now as most
people will simply be updating existing set-ups, and we should be recommending
5.4 for new installations anyway?
--
Lester Caine - G8HFL
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
Kris Craig wrote:
I'll commit the changes to 5.4 at the earliest opportunity. I just
realized that the language was somewhat vague as to whether it should be
applied to 5.3 branch or not; I don't really care either way but I'll
probably just go ahead and apply it to both unless anyone has any
objections.Any reason to change the 'logic' of 5.3 now? Having already been hit by a
5.4 change that has not been back-ported, some consistency on what is and
isn't would be helpful, and I don't think there is any point changing this
now as most people will simply be updating existing set-ups, and we should
be recommending 5.4 for new installations anyway?--
Lester Caine - G8HFLContact - http://lsces.co.uk/wiki/?page=**contacthttp://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/**index.phphttp://www.firebirdsql.org/index.php--
Hmm good point. Ok, you've convinced me. I'll only apply it to 5.4. =)
--Kris