PEAR Packages

[gareth_western]

Is it possible for us to install new PEAR packages with the installation? There are a few that I'd like to use in a couple of Web projects for some clients, which would make the coding a lot easier.

Cheers

[Buddha]

PEAR Packages would probably be ok. PECL Packages would most likely not be ok. Ask Dathorn support about specific packages.

[sdjl]

If you mean PEAR as in PHP pear (http://pear.php.net) then that should be fine. It is after all just PHP code

David

[gareth_western]

Yes, I was referring to PEAR for PHP.

Pardon my ignorance, but why PEAR and not PECL? Are they not both just repositories of scripts?

So how can I install a PEAR package? The usual "PEAR install <script>" command won't work because I don't have permission to write to the appropriate directories...

-jailshell-2.05b$ pear install Contact_Vcard_Build
downloading Contact_Vcard_Build-1.1.tgz ...
Starting to download Contact_Vcard_Build-1.1.tgz (11,747 bytes)
.....done: 11,747 bytes
failed to write /usr/local/lib/php/.tmpContact_Vcard_Build.php

The package I would like to install can be found at http://pear.php.net/package/Contact_Vcard_Build

Thanks for the help/info!

[gareth_western]

duh

oh... duh.. I guess I just download the package files seperately and install them in my own space, setting up my own include paths?

[Buddha]

Pardon my ignorance, but why PEAR and not PECL? Are they not both just repositories of scripts?

PECL is a repository for PHP Extensions and aren't PHP scripts. PHP comes with a number of extension like MySQL and PCRE. These extension are usually written in a compiled language such as C or C++. Since they need compiling - you can't install PECL's yourself at Dathorn.

The only reason I mentioned PECL is until last year PECL and PEAR packages were hosted together on one site.

oh... duh.. I guess I just download the package files seperately and install them in my own space, setting up my own include paths?

That sounds right.

Good luck.

[sdjl]

oh... duh.. I guess I just download the package files seperately and install them in my own space, setting up my own include paths?

That is correct