public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <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:49:25 -0500	[thread overview]
Message-ID: <CAGfcS_mc0d8DTW54WA71c-Ecz3k_ZEZExF7jDfWuHJfy_0c4Ww@mail.gmail.com> (raw)
In-Reply-To: <568AAA13.8080006@gentoo.org>

On Mon, Jan 4, 2016 at 12:21 PM, Brian Evans <grknight@gentoo.org> wrote:
>
> 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"?
>

My understanding (which could be wrong) is that this update will break
things even if the user never runs eselect php afterwards.  I can't
tell you the last time I touched the php eselect module, because major
updates to php are rare.



-- 
Rich


  reply	other threads:[~2016-01-04 17:49 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 [this message]
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=CAGfcS_mc0d8DTW54WA71c-Ecz3k_ZEZExF7jDfWuHJfy_0c4Ww@mail.gmail.com \
    --to=rich0@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