public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: Lars Wendler <polynomial-c@gentoo.org>
Cc: Sebastian Pipping <sping@gentoo.org>,
	gentoo-dev <gentoo-dev@lists.gentoo.org>,
	"pr@gentoo.org" <pr@gentoo.org>
Subject: Re: [gentoo-dev] News item: Apache "-D PHP5" needs update to "-D PHP"
Date: Mon, 4 Jan 2016 14:40:36 +0100	[thread overview]
Message-ID: <20160104144036.1083a3d1.mgorny@gentoo.org> (raw)
In-Reply-To: <20160104114537.392b9971@shanghai.paradoxon.rec>

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

On Mon, 4 Jan 2016 11:45:37 +0100
Lars Wendler <polynomial-c@gentoo.org> wrote:

> to be honest I was very upset when I first stumbled upon this problem.
> And yes I only found about it when my apache webserver started to
> deliver php source code instead of the real sites.
> Doing such a change without getting in contact with me as apache
> maintainer before the change was done is very... eh... impolite at best.

Well, if this is the common outcome, then I dare say it's very bad,
at least. Gentoo was never the distribution people could seriously
consider stable, and it not uncommon for breakages like this to happen.
But still, it's very bad if an upgrade is going to suddenly cause
webserver to disclose script sources rather than running it.

While of course the sole fact that this can happen is a complete
disastrous design failure, we can't really do much about it or cause
people to stop using such misdesigned software. Nevertheless, I think
it would be reasonable to at least try to reduce the intentional
breakage to bare minimum.

Therefore, I think you should really work on some kind of backwards
compatibility for people using '-D PHP5' that would prevent those kind
of issues at least for some migration period. With big fat warnings for
people who run it.

-- 
Best regards,
Michał Górny
<http://dev.gentoo.org/~mgorny/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 949 bytes --]

  reply	other threads:[~2016-01-04 13:41 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 [this message]
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
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=20160104144036.1083a3d1.mgorny@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=polynomial-c@gentoo.org \
    --cc=pr@gentoo.org \
    --cc=sping@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