I see that there are a plethora of php extensions available as rpms, from the centos repositories, but not the php-mcrypt extension. I'm trying to stick to an rpm-only system and haven't found one that provides this, yet, for my 4.4 system.
Is there any plan to add this to the repository in the near future (if at all)? Does anyone know where I can get it, otherwise? I see there is one for FC4. Perhaps I can do a --rebuild on it?
On 11/8/06, Shaun T. Erickson sterickson@gmail.com wrote:
I see that there are a plethora of php extensions available as rpms, from the centos repositories, but not the php-mcrypt extension. I'm trying to stick to an rpm-only system and haven't found one that provides this, yet, for my 4.4 system.
http://phprpms.sourceforge.net/ This requires rpmforge/dag.wieers.com repositories to be enabled so that libmcrypt can be installed.
On 11/8/06, Jim Perrin jperrin@gmail.com wrote:
http://phprpms.sourceforge.net/ This requires rpmforge/dag.wieers.com repositories to be enabled so that libmcrypt can be installed.
Yup. I already installed libmcrypt from rpmforge, before posting. I had also visited the site you mention, but there is only an FC4 rpm there and no srpm to rebuild from to make one for my system, so I'm still stumped. Or can I just install the FC4 rpm?
On 11/8/06, Shaun T. Erickson sterickson@gmail.com wrote:
On 11/8/06, Jim Perrin jperrin@gmail.com wrote:
http://phprpms.sourceforge.net/ This requires rpmforge/dag.wieers.com repositories to be enabled so that libmcrypt can be installed.
Yup. I already installed libmcrypt from rpmforge, before posting. I had also visited the site you mention, but there is only an FC4 rpm there and no srpm to rebuild from to make one for my system, so I'm still stumped. Or can I just install the FC4 rpm?
Huh? It lists rpms for the following: FC4 FC3 FC2 RHEL3 RHEL4 RHEL4-x86_64 php-mcrypt-5.0.4-10.1.i386.rpm php-mcrypt-4.3.11-2.5.1.i386.rpm php-mcrypt-4.3.10-2.4.2.i386.rpm php-mcrypt-4.3.2-26.ent.1.i386.rpm php-mcrypt-4.3.9-3.2.1.i386.rpm php-mcrypt-4.3.9-3.9.1.x86_64.rpm
On 11/8/06, Jim Perrin jperrin@gmail.com wrote:
Huh? It lists rpms for the following: FC4 FC3 FC2 RHEL3 RHEL4 RHEL4-x86_64
php-mcrypt-5.0.4-10.1.i386.rpm php-mcrypt-4.3.11-2.5.1.i386.rpm php-mcrypt-4.3.10-2.4.2.i386.rpm php-mcrypt-4.3.2-26.ent.1.i386.rpm php-mcrypt-4.3.9-3.2.1.i386.rpm php-mcrypt-4.3.9-3.9.1.x86_64.rpm
My system is running php 5.0.4. It and all the other php-* rpms on my system are 5.0.4-5. The only 5.04 rpm on that site is the one for FC4, and there is no srpm that I might recompile for use on my system.
Shaun T. Erickson wrote:
I see that there are a plethora of php extensions available as rpms, from the centos repositories, but not the php-mcrypt extension. I'm trying to stick to an rpm-only system and haven't found one that provides this, yet, for my 4.4 system.
Is there any plan to add this to the repository in the near future (if at all)? Does anyone know where I can get it, otherwise? I see there is one for FC4. Perhaps I can do a --rebuild on it?
Get SRPM for PHP. Edit the php.spec file and add subpackages for any extensions you might want, and rebuild using that spec file. The php.spec file is nicely organized. What you need to change is the configure command (add extensions you want), and define new subpackages for your extensions (copy&paste definitions for existing subpackages and change names). It's fairly trivial. If you have problems with editing it, let me know and I could send you the php.spec file I'm using (that has mcrypt extension enabled among other things).
BTW, once you have "custom" PHP subpackage installed (for example php-mcrypt), you'll have to rebuild it by hand every time there is a security update. The dependencies will prevent automatic upgrade of main php package (php-* subpackages always depend on exactly the same version of main php package). There's an update for PHP coming (Red Hat already released it for RHEL4). You might want to wait for a day or two for CentOS to release it, and than rebuild.
On 11/8/06, Aleksandar Milivojevic alex@milivojevic.org wrote:
Get SRPM for PHP. Edit the php.spec file and add subpackages for any extensions you might want, and rebuild using that spec file. The php.spec file is nicely organized. What you need to change is the configure command (add extensions you want), and define new subpackages for your extensions (copy&paste definitions for existing subpackages and change names). It's fairly trivial.
Ok. I'll do that.
BTW, once you have "custom" PHP subpackage installed (for example php-mcrypt), you'll have to rebuild it by hand every time there is a security update.
This is one of the reasons why I was advocating for it to be built by the CentOS team and added to the repository along with the other subpackages. Not that I mind doing it, but then it would just 'be there', available to anyone who needed/wanted it. The particular reason I'm looking for it is that phpMyAdmin can use it.
-ste
On 11/8/06, Shaun T. Erickson sterickson@gmail.com wrote:
On 11/8/06, Aleksandar Milivojevic alex@milivojevic.org wrote:
Get SRPM for PHP. Edit the php.spec file and add subpackages for any extensions you might want, and rebuild using that spec file. The php.spec file is nicely organized. What you need to change is the configure command (add extensions you want), and define new subpackages for your extensions (copy&paste definitions for existing subpackages and change names). It's fairly trivial.
Ok. I'll do that.
This process worked quite nicely. Thanks. :)
On Wed, 8 Nov 2006, Shaun T. Erickson wrote:
there', available to anyone who needed/wanted it. The particular reason I'm looking for it is that phpMyAdmin can use it.
*cough* run phpMyAdmin at http://nvd.nist.gov/nvd.cfm ---- This seems unwise.
-- Russ Herrold
On Thu, 2006-11-09 at 23:12 -0500, R P Herrold wrote:
On Wed, 8 Nov 2006, Shaun T. Erickson wrote:
there', available to anyone who needed/wanted it. The particular reason I'm looking for it is that phpMyAdmin can use it.
*cough* run phpMyAdmin at http://nvd.nist.gov/nvd.cfm ---- This seems unwise.
---- at least without adequate safeguards such as restricting usage by user/host/ssl etc.
Craig
On Fri, 10 Nov 2006, Craig White wrote:
On Thu, 2006-11-09 at 23:12 -0500, R P Herrold wrote:
*cough* run phpMyAdmin at http://nvd.nist.gov/nvd.cfm ---- This seems unwise.
at least without adequate safeguards such as restricting usage by user/host/ssl etc.
The package's history looks like a malarial swamp; I think it calls out for a packaging intervention, adding a mandatory iptables drop rule on all but 127.0.0.1 ;)
- R