From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] News item: Apache "-D PHP5" needs update to "-D PHP"
Date: Sat, 9 Jan 2016 12:39:09 -0500 [thread overview]
Message-ID: <569145BD.7000607@gentoo.org> (raw)
In-Reply-To: <20160108005219.GN11262@schiffbauer.net>
On 01/07/2016 07:52 PM, Marc Schiffbauer wrote:
>>
>> 3. I could try to hack some magic into eselect-php to detect whether or
>> not you have -DPHP5 set. Something simple, like grepping /etc/conf.d
>> /apache2 for "PHP5". In that case we could omit a notice.
>> This one simultaneously makes the most sense and feels like the
>> biggest hack.
>
> +1 for 3.
>
> You can remove the hack in a year or so. I think most important is a
> good user experience. If this requires a hack because the design of the
> tools give you no other choice than be it.
>
Done in recent eselect-php:
$ sudo eselect php set apache2 1
!!! Warning: The apache2 configuration has changed in this
!!! Warning: version of eselect-php. You should define "-D PHP"
!!! Warning: and not "-D PHP5" for apache. The module is now
!!! Warning: loaded by 70_mod_php.conf (was 70_mod_php5.conf).
!!! Warning: After you have changed "-D PHP5" to "-D PHP",
!!! Warning: you should remove 70_mod_php5.conf to eliminate
!!! Warning: this warning. Until you have done so, your eselect
!!! Warning: choices for apache2 will have no effect.
Please restart apache for the changes to take effect.
Users may get that warning more than once if we reinstall
70_mod_php5.conf, but it's harmless and less hacky than grepping
/etc/conf.d/apache2.
I think we can forego the news item? Thanks for the suggestions.
next prev parent reply other threads:[~2016-01-09 17:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 0:26 [gentoo-dev] News item: Apache "-D PHP5" needs update to "-D PHP" Sebastian Pipping
2016-01-04 5:11 ` Jeroen Roovers
2016-01-04 16:53 ` Michael Orlitzky
2016-01-04 8:41 ` [gentoo-dev] " Kristian Fiskerstrand
2016-01-04 12:11 ` Rich Freeman
2016-01-04 13:30 ` Kristian Fiskerstrand
2016-01-04 14:20 ` Kristian Fiskerstrand
2016-01-04 14:51 ` Rich Freeman
2016-01-04 14:45 ` Peter Stuge
2016-01-04 15:08 ` Brian Evans
2016-01-04 10:45 ` [gentoo-dev] " Lars Wendler
2016-01-04 13:40 ` Michał Górny
2016-01-04 15:20 ` Michael Orlitzky
2016-01-04 15:42 ` Peter Stuge
2016-01-04 15:53 ` Michael Orlitzky
2016-01-04 16:11 ` Peter Stuge
2016-01-04 16:43 ` Michael Orlitzky
2016-01-04 17:21 ` Brian Evans
2016-01-04 17:49 ` Rich Freeman
2016-01-04 19:27 ` Michael Orlitzky
2016-01-05 19:35 ` Michael Orlitzky
2016-01-06 19:36 ` Sebastian Pipping
2016-01-06 19:53 ` Michael Orlitzky
2016-01-08 0:52 ` Marc Schiffbauer
2016-01-09 17:39 ` Michael Orlitzky [this message]
2016-01-06 19:39 ` Sebastian Pipping
2016-01-04 15:11 ` Hanno Böck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=569145BD.7000607@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox