public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: php4 vs php5
Date: Wed, 15 Mar 2006 09:03:12 +0000	[thread overview]
Message-ID: <20060315090312.066762a8@krikkit.digimed.co.uk> (raw)
In-Reply-To: <loom.20060315T042120-689@post.gmane.org>

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

On Wed, 15 Mar 2006 03:35:49 +0000 (UTC), James wrote:

> > dev-php is on it's way out and has not been updated in some time.
> > You're likely vulnerable at this moment.
> 
> Um, I must not have been clear. JFFNMS is critical. It requires php4.
> so upgrading to php5 is NOT an option, until the JFFNMS devs move
> to php5.

Yes, but you need dev-lang/php-4*, not dev-php/php-4*. Unmerge the
blockers and dev-lang/php-4* will emerge. You don't need mod_php anymore,
it is provided by the apache(2) USE flags of dev-lang/php.

If the JFFNMS ebuild explicitly depends on dev-php/php, it is broken.
file a bug and add it to /etc/portage/profile/package.provided to work
around it until it is fixed (or fix the ebuild yourself).


-- 
Neil Bothwick

Another casualty of applied metaphysics.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

  parent reply	other threads:[~2006-03-15  9:09 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
2006-03-15  3:35   ` [gentoo-user] " James
2006-03-15  3:45     ` kashani
2006-03-15  9:03     ` Neil Bothwick [this message]
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=20060315090312.066762a8@krikkit.digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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