Re: installing PECL extensions via "pecl" versus fedora packages

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Feb 19, 2010 at 14:12, Robert P. J. Day <rpjday@xxxxxxxxxxxxxx> wrote:
>  so the question is, given that installing via the "pecl" command
> gives one access to hundreds of possible PHP extensions, what's the
> rationale behind that small number of fedora-packaged extensions?  is
> there some reason someone decided to pre-package just those?  just
> curious.

Yes, that is the only reason. It is the same with the "pear" command.

The advantage of RPMs is that it will also pull in libraries (like the
memcache libs) which are needed for the pecl package. And they will be
updated with the rest of the system through yum.

The disadvantage is that it is a bit of work to get them packaged (and
maintained) for Fedora.

I stopped installing non RPM software on Fedora / RHEL a few years
ago, because I want the power of RPM and for private use it is quite
easy to create a quick and dirty RPM from a pecl or pear package. And
once you got that it is easy to install on multiple machines too.

Christof
-- 
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux