public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Stuge <peter@stuge.se>
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 17:11:53 +0100	[thread overview]
Message-ID: <20160104161153.30168.qmail@stuge.se> (raw)
In-Reply-To: <568A9592.5090401@gentoo.org>

Michael Orlitzky wrote:
> >> If anyone has a concrete idea that works better, it's not too late to
> >> change it.
> > 
> > Add code to init script and service file to check the config before
> > starting the program, and react if PHP5 is still set.
> 
> Which init script?

For Apache.

> It's only "bad" to have PHP5 set if the user has installed
> >=eselect-php-0.8.1, and run it at least once.

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?


> You don't want to e.g. kill working php-5.x installations for people
> who have apache keyworded ~arch.

IMO that would be a much lesser evil than serving source in another
case, as long as it is clear how to unkill (sed s,PHP5,PHP,) the setup.


//Peter


  reply	other threads:[~2016-01-04 16:12 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 [this message]
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
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=20160104161153.30168.qmail@stuge.se \
    --to=peter@stuge.se \
    --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