public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ole Markus With <olemarkus@olemarkus.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] PHP targets
Date: Tue, 17 May 2011 10:05:34 +0200	[thread overview]
Message-ID: <4DD22C4E.4030508@olemarkus.org> (raw)
In-Reply-To: <BANLkTi==_n8TG2SJxYiCqLZMujpt2GBJGw@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 16/05/11 08:43, Dirkjan Ochtman wrote:
> I just tried to update one of my systems, and the emerge -uavDN world
> failed due to the requirement of php_targets_php5-2. Now, I do have
> php installed on this box, but I had never set the targets so far.
> Perhaps a news item or some other notification for this kind of stuff
> wouldn't be out of order? Now I had to go googling for php targets. I
> found the upgrading guide, but it seems kind of annoying that we don't
> provide more guidance if we're going to mandate some more
> configuration on the part of unsuspecting users.
> 

Hi Dirkjan,

At the time we released the "new" PHP ebuilds, we felt that the
post-install instructions were good enough as a source of information.
This one has a warning about setting PHP_TARGETS as well as a link to
the upgrade guide. PHP_TARGETS had already been set to a sane default in
all profiles so we believed that this should be a smooth update for our
users.

And indeed, we have not had much support issues on this. All the issues
I can think of happened to users after upgrading PHP, meaning they most
definitely did not read the post-install instructions.

The worst-case is that users have to google in order to find out what
all this PHP_TARGETS business is, where they will find their answers
quite quickly

So far, I have only seen news items where stuff may actually break. In
this case it is more about not being able to upgrade because PHP_TARGETS
is not set properly, where portage gives you warning about what to do.
As I said, we have not really had much issues with this.

Cheers,
Ole Markus
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJN0ixNAAoJEGurSuXEqSv1chUIAIlhxd23QiRU7xziKuQEGheD
L9SIE53M8V8ZAT9Un+0TEC0CNq4MF8XLSPJDrAmzEKX0zL2TaRVTPcNhGulgmhjF
VTqBqhQosUAlquY4eVfV7tuCXFt6BJwdlL9b0p7eFwhdketFGZkHNOcv5RrJHxj6
/oYnGZq7EsqoBQJCyyc4QMHDmCBfF2lyBcG40EsK9eVCx1xnVbnhCwlMQPMBYtQw
F7DDnjjYHbT06AiGOiz2KPV8cmLqcF1AKC779NZXjCdvtkiEHjzpjqeNwgJMZu1c
x3GAFWVkF3txUbC0NdOA8IKnwBtKPHMCzHD40339XAYzOFN6fNPjJisizblIhMs=
=Rixa
-----END PGP SIGNATURE-----



      reply	other threads:[~2011-05-17  8:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16  6:43 [gentoo-dev] PHP targets Dirkjan Ochtman
2011-05-17  8:05 ` Ole Markus With [this message]

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=4DD22C4E.4030508@olemarkus.org \
    --to=olemarkus@olemarkus.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