From Fedora at FamilleCollet.com  Mon Sep  3 13:59:06 2007
From: Fedora at FamilleCollet.com (Remi Collet)
Date: Mon, 03 Sep 2007 15:59:06 +0200
Subject: [Fedora-php-devel-list] PHP extension in EL4 
Message-ID: <46DC132A.8070604@FamilleCollet.com>

I've a look to PHP and extensions in EL4.

We have a lot "PEAR" and PECL extensions in EPEL for EL5 which cannot go
to EPEL for EL4 because of very old PHP and PEAR version.

RHEL 4 users can use packages from RHWAS (Web Application Stack 1.0)
ftp://ftp.redhat.com/pub/redhat/linux/enterprise/4/en/RHWAS/SRPMS
ftp://ftp.redhat.com/pub/redhat/linux/updates/enterprise/4ES/en/RHWAS/SRPMS

We found there
- php-5.1.6 (as for RHEL5)
- pear-1.4.11

CentOS 4 users can use packages from centosplus repository
We found there all RHWAS RPM and a lot of RPM from Fedora/EPEL (i've
read some changelog to verify)
http://isoredirect.centos.org/centos/4/centosplus/SRPMS/

I think the packages from EPEL-5 could easily be maintain for an EPEL-4+
repository (using RHEL + RHWAS as references).

I also think it's quite strange than CentOS repository is more complete
than EPEL using only RHEL + Fedora community work...


What must we do in EPEL-4 ?
Regards



From fedora at theholbrooks.org  Fri Sep  7 05:31:25 2007
From: fedora at theholbrooks.org (Brandon Holbrook)
Date: Fri, 07 Sep 2007 00:31:25 -0500
Subject: [Fedora-php-devel-list] Re: rpms/php-pear-Mail-Mime/devel
 .cvsignore, 1.3, 1.4 php-pear-Mail-Mime.spec, 
 1.2, 1.3 sources, 1.3, 1.4
In-Reply-To: <46E0DD02.7040505@FamilleCollet.com>
References: <200709060548.l865mvTG020300@cvs-int.fedora.redhat.com>
	<46E0DD02.7040505@FamilleCollet.com>
Message-ID: <46E0E22D.2050307@theholbrooks.org>

Remi Collet wrote:
> Brandon Holbrook (static) a ?crit :
>   
>> -BuildRequires:	php-pear >= 1:1.4.9-1.2
>> +BuildRequires:	php-pear >= 1.6.0
>>  Requires:	php-pear(PEAR)
>>   
>>     
> You should probably keep "epoch" in this BR
>
> BuildRequires:	php-pear >= 1:1.6.0
> or 
> BuildRequires:	php-pear(PEAR) >= 1.6.0
>
> (to avoid build on EL4, with php-pear 0:4.3.9)
>
> But, is it really a BuildRequires or a Requires ?
>
> Regards.
>
>   
Thanks Remi, good eye.  I tried to find another pear package in devel 
that was taking advantage of the new pear 1.6 to use as a template, but 
couldn't find one.  I've updated Mail-Mime to read:

BuildRequires:	php-pear >= 1:1.4.9-1.2
Requires:	php-pear(PEAR) >= 1.6.0

Since you are correct that I technically only need 1.6 at run time, not 
build time.  BUT now that I stare at that for a moment.... is Requires 
enough, or should it actually be Requires(post) since this version of 
Mail_Mime needs to use pear 1.6 at rpm install time and not just run 
time?  Is that already implied through my Requires(post): %{__pear}, or 
does that still ignore corner cases like updating from f[0-7]->f8?  If 
you try to install Mail_Mime 1.5.x on f7 you get "pear/Mail_Mime 
requires PEAR Installer (version >= 1.6.0), installed version is 1.5.0"  
Thoughts?  Any other pear packagers crossed this bridge already in rawhide?