public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: kashani <kashani-list@badapple.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  php4 vs php5
Date: Tue, 14 Mar 2006 18:11:12 -0800	[thread overview]
Message-ID: <441777C0.8000106@badapple.net> (raw)
In-Reply-To: <loom.20060315T021622-196@post.gmane.org>

James wrote:
> Calculating dependencies ...done!
> [blocks B     ] dev-php/mod_php (is blocking dev-lang/php-4.4.2)
> [blocks B     ] dev-php/php (is blocking dev-lang/php-4.4.2)
> [ebuild  N    ] dev-lang/php-4.4.2 


dev-php is on it's way out and has not been updated in some time. You're 
likely vulnerable at this moment.


> So the question is what do I put in /etc/portage/? file to get
> the system to accept the older dev-php files and not try to install
> 'dev-lang/php' ?

You don't. You remove dev-php and install dev-lang/php when you have 
some time to deal with change. I had no issues moving from dev-php to 
dev-lang/php with 4.4.x and the whole thing took about 30 minutes. 
Didn't even have downtime as Apache had the old module cached until I 
stopped and started to pick up the new build.

However PHP USE flags have gotten a bit more complex. You'll want apache 
(or apache2), cli for the php commandline binary, and session at minimum 
plus anything else you might need.

kashani
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-03-15  2:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-15  1:35 [gentoo-user] php4 vs php5 James
2006-03-15  1:59 ` JimD
2006-03-15  2:00 ` Michael Stewart (vericgar)
2006-03-15  2:11 ` kashani [this message]
2006-03-15  3:35   ` [gentoo-user] " James
2006-03-15  3:45     ` kashani
2006-03-15  9:03     ` Neil Bothwick
2006-03-15 16:32       ` James
2006-03-16  1:34       ` kashani
2006-03-16 17:36         ` James
2006-03-16 18:18           ` kashani

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=441777C0.8000106@badapple.net \
    --to=kashani-list@badapple.net \
    --cc=gentoo-user@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