Re: php-pear .rpm install format

Hello, On 10/03/2002 08:49 AM, Michael Dransfield wrote:

I agree... There is no reason why people couldn't make rpm's for the classes (or collections of classes/the entire repository). The RPM could even just be a script which does 'pear install Blah', or you could write a bash equivalent of the pear install command. MD5 checksums could easily be added at a later point, although at the moment since all classes are downloaded from the same source, it is unlikely that they will be contaminated at source (such a thing would easilly be spotted any rectified). If downloads are contaminated through local dns spoofing, then that is another security problem (not one of PEAR's)

That is no reason to requiring security packages. To demonstrate my point, just read the latest CERT warning regarding the version of sendmail that was hacked and replace in the very sendmail.org site.

Making PEAR depend on RPM in my opinion is bad because it ties PHP to linux, whereas PHP is designed to run on ALL OS's. What about using debian packaging system? (I hear its better than RPM anyway...)

Using RPM format does not tie you more to any platform than using tar.gz format. You are confusing a file format with the platform it was originated. Data is data and should not be confused with the programs or platforms that use it. -- Regards, Manuel Lemos