From: Yves Thommes <doc@foobar.lu>
To: gentoo-server@lists.gentoo.org
Subject: Re: [gentoo-server] PHP4
Date: Tue, 22 Jan 2008 21:37:07 +0100 [thread overview]
Message-ID: <479653F3.4040304@foobar.lu> (raw)
In-Reply-To: <479651CC.7040605@gentoo.org>
i really don't want to start splitting hairs here, but on 2007-07-13 the
php team did the following announcement:
[quote]
The PHP development team hereby announces that support for PHP 4 will
continue until the end of this year only. After 2007-12-31 there will be
no more releases of PHP 4.4. We will continue to make critical security
fixes available on a case-by-case basis until 2008-08-08. Please use the
rest of this year to make your application suitable to run on PHP 5.
[/quote]
so i suppose the support period was announced together with the EOL news
but ok, i get the point that you want people to update to php5 asap.
Andrew Gaffney wrote:
> Yves Thommes wrote:
>> regarding the php4 ebuild i was a little bit surprised that they
>> would drop the ebuild so soon, after all php4 will still get security
>> fixes until 2008-08. i was wondering, if they keep mysql-4.0 in
>> portage which isn't supported anymore since summer 2006, why would
>> they want to drop php4 so quickly?
>
> Because this "stay of execution" was announced after the decided to
> EOL php4. Gentoo dropped the php4 support after the original
> announcement was made. We're not going to temporarily bring them back
> just for a couple of months.
>
--
gentoo-server@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-01-22 20:37 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 16:10 [gentoo-server] PHP4 A. Khattri
2008-01-18 16:12 ` Petteri Räty
2008-01-18 16:48 ` Jil Larner
2008-01-18 17:29 ` Lindsay Haisley
2008-01-22 16:13 ` Yves Thommes
2008-01-22 16:19 ` Andrew Gaffney
2008-01-22 18:12 ` Lindsay Haisley
2008-01-22 18:38 ` Yves Thommes
2008-01-22 18:53 ` Georges Toth
2008-01-22 18:55 ` Georges Toth
2008-01-22 19:13 ` Lindsay Haisley
2008-01-22 19:18 ` RijilV
2008-01-22 19:30 ` Lindsay Haisley
2008-01-22 19:42 ` Georges Toth
2008-01-22 20:22 ` Yves Thommes
2008-01-22 20:27 ` Andrew Gaffney
2008-01-22 20:37 ` Yves Thommes [this message]
2008-01-22 20:47 ` Qian Qiao
2008-01-22 21:12 ` Lindsay Haisley
2008-01-22 21:18 ` Andrew Gaffney
2008-01-22 23:02 ` Yves Thommes
2008-01-22 23:11 ` Qian Qiao
2008-01-22 23:15 ` RijilV
2008-01-22 23:41 ` Chashab
2008-01-23 8:37 ` Dumitru Moldovan
2008-01-23 0:39 ` Georges Toth
2008-01-22 21:42 ` pkoelle
2008-01-22 21:58 ` RijilV
2008-01-22 19:35 ` Georges Toth
2008-01-22 19:43 ` Greg Bowser
2008-01-22 19:46 ` Georges Toth
2008-01-22 19:48 ` Andrew Gaffney
2008-01-22 19:59 ` Greg Bowser
2008-01-22 19:54 ` Thilo Bangert
2008-01-22 19:56 ` Georges Toth
2008-01-22 19:10 ` Lindsay Haisley
2008-01-22 19:58 ` Thilo Bangert
2008-01-22 23:45 ` Yves Thommes
2008-01-23 0:00 ` Qian Qiao
2008-01-23 0:07 ` Lindsay Haisley
2008-01-22 18:16 ` Yves Thommes
2008-01-22 20:13 ` Petteri Räty
2008-01-22 20:31 ` Yves Thommes
2008-01-22 20:38 ` Qian Qiao
2008-01-22 20:46 ` Andrew Gaffney
2008-01-22 21:19 ` Lindsay Haisley
2008-01-22 21:20 ` Andrew Gaffney
2008-01-22 21:23 ` Lindsay Haisley
2008-01-22 21:35 ` Oliver Schad
2008-01-22 16:36 ` RijilV
2008-01-22 19:39 ` Matthias Bethke
2008-01-23 15:02 ` Matthew Summers
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=479653F3.4040304@foobar.lu \
--to=doc@foobar.lu \
--cc=gentoo-server@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