public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marc Schiffbauer <mschiff@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] News item: Apache "-D PHP5" needs update to "-D PHP"
Date: Fri, 8 Jan 2016 01:52:19 +0100	[thread overview]
Message-ID: <20160108005219.GN11262@schiffbauer.net> (raw)
In-Reply-To: <568D70C7.5080007@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1598 bytes --]

* Michael Orlitzky schrieb am 06.01.16 um 20:53 Uhr:
> On 01/06/2016 02:36 PM, Sebastian Pipping wrote:
> > On 05.01.2016 20:35, Michael Orlitzky wrote:
> >> I just pushed a new revision with this fix. In eselect-php-0.8.2-r1,
> >> we ship both the new 70_mod_php.conf and the old 70_mod_php5.conf. The
> >> latter comes with a big warning at the top of it, stating that it is for
> >> backwards compatibility only.
> > 
> > Cool, sounds like a great idea to me.
> > 
> > I guess we don't need a news item any more then?
> > 
> 
> Upgraders still have a problem, but a much less severe one. After
> upgrading eselect-php, further attempts to `eselect php set apache2`
> will appear to have no effect, because the old 70_mod_php5.conf is
> loading the old symlink to libphp5.so. There are a few options:
> 
> 1. Leave things as is, and tell people what to do (read the elog) if
>    they hit this situation.
> 
> 2. Proceed with a news item that basically says "read the elog."
> 
> 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.


-- 
0x35A64134 - 8AAC 5F46 83B4 DB70 8317
             3723 296C 6CCA 35A6 4134

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-01-08  0:52 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 [this message]
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=20160108005219.GN11262@schiffbauer.net \
    --to=mschiff@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