From: Brian Evans <grknight@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] News item: Apache "-D PHP5" needs update to "-D PHP"
Date: Mon, 4 Jan 2016 12:21:23 -0500 [thread overview]
Message-ID: <568AAA13.8080006@gentoo.org> (raw)
In-Reply-To: <568AA12D.7090807@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 1/4/2016 11:43 AM, Michael Orlitzky wrote:
> On 01/04/2016 11:11 AM, Peter Stuge wrote:
>>
>> So pkg_postinst for >=eselect-php-0.8.1 should say something,
>> but ideally also the invocation - but I don't know if eselect-php
>> is also code or only data managed by eselect?
>
> The pkg_postinst is already there. The eselect-php routines are
> bash code so theoretically we can do anything we want. How do
> people feel about making eselect-php spit out a warning every time
> the apache2 module is messed with?
Perhaps grep for -DPHP5 or if -DPHP is missing in the conf.d and shout
then as part of the "eselect php set apache2 X"?
Brian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
iQIcBAEBAgAGBQJWiqoTAAoJENH3ge/59KO2XRUP/RFybVPuCNtCDEPclsKWp5AI
rvejArURHwk8hu+OjITLb/0UxYM5VwXN9fOrSkxJ3lsVErNlxfeaLc0UYYh/1qnd
WeofmCq7yx0enOe0+szcY877reca5yfPzPs3ChB+a4+PpVAIuD7quL0lcuhs/NMJ
S9Hoex5mOmmd82jeXdZlvZZzLHxLhsnWwTjDQhmnCL9mkHbx2u1+07et7Wdxd8Gu
Td4O9tiAvp/5KQ3Dmw2P2BQPBbZc0EYqGG/Aghw02dDHp+jq5snVRXCdg/z1L61j
VXPblbNBRY9wA96k0vu6aqGRWGuj66rBHcF3DH8A9+o0LY/8eh9v56n7UGg2LfE8
5GEgfT4yY7d5DYEikWKLc56iOy754auh0UbXC+5IaAK8PfIOcMBFG1AgvEqZY+VU
pXBF7yh1QxaAtsYBjKX8X+DuCr9549vjSsMKtUFN+mCz1cLi1KX9OxtCvVQMJUnM
zx5mK8JNFoKlA/kINERsa//swICDgJ2aN4GX64YV+tnfsrZrM1YSJxHIjiEE7Q1m
Pd3v/0CFMra5snYEMdk8qoYQ7ITQdmsM0vM93OgqBYmaNrEZlNG5T+seMpPxv+lD
BhT8R7W2mDqKShljjm31nzp4FG/30z8DymeBn+JVWxHbdy5IqUlaYa5egpWk1vip
qw0h5uqKkkv6BKwXI8sp
=60JD
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-01-04 17:20 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 [this message]
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
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=568AAA13.8080006@gentoo.org \
--to=grknight@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