Bug 103006 - [RFE] Upgrade PHP and MyQL packages for web servers
Summary: [RFE] Upgrade PHP and MyQL packages for web servers
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: php   
(Show other bugs)
Version: 4.2
Hardware: All Linux
Target Milestone: ---
Assignee: Joe Orton
QA Contact: David Lawrence
Keywords: FutureFeature
Depends On:
TreeView+ depends on / blocked
Reported: 2003-08-25 07:24 UTC by François Gutierrez
Modified: 2007-03-27 04:09 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-01-13 15:37:13 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description François Gutierrez 2003-08-25 07:24:57 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 

Description of problem:
Our company chose RH9 for its Apache/PHP/MySQL web servers and decided for RHN 
support with full auto-update feature.

We are very disappointed not having PHP 4.3.x nor MySL 4.x available packages, 
and the answers in bugzilla ("depends on product managers") isn't satisfiying. 
Our developper must write some functions to emulate PHP 4.3.x new ones.

How about PHP5, shall we resigned from RHN and manage ourselves, maybe cheaper 
than "emulating" or "working around" releases...

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. N/A

Additional info:

Comment 1 Joe Orton 2003-08-29 14:31:58 UTC
Future releases will include php-4.3; the "Severn" and "Taroon" beta releases
both include 4.3.2.

We can't upgrade to MySQL 4.0 for licensing reasons.  (it's not legal to
redistribute a php which is linked against MySQL 4.0, for instance)

Comment 2 Joe Orton 2004-01-13 15:37:13 UTC
Fedora Core 1 shipped with php-4.3.3, and php-4.3.4 is available as
the current update release for FC1.

Note You need to log in before you can comment on or make changes to this bug.