Re: Installer problems

From: Date: Sat, 23 Mar 2002 18:26:12 +0000
Subject: Re: Installer problems
References: 1 2  Groups: php.pear.general 
Request: Send a blank email to pear-general+get-1036@lists.php.net to get a copy of this message
Martin Jansen wrote: > > On Thu, 21 Mar 2002 14:14:49 -0600 (CST), Brent Cook wrote: > > > > >Or to draw a closer parallel, like the Perl CPAN installer? Good, I really > >like that one. I'm sure that distribution folks would also appreciate it > >if individual Pear modules installable by this tool were available at some > >time as plain tarballs too, like CPAN modules are (to make it easy to > >either use the Pear installer, or integrate into an existing package > >system). PEAR packages are really tar.gz files and the installer was built in mind to be easily integrable in other packages systems like RPM, DEB, etc. And yes, it's usage mode is very easy. Just for giving some examples: Local install # pear install HTTP_Upload-1.0.tgz Remote install # pear install http://pear.php.net/get/HTTP_Upload-1.0.tgz Install the lastest version from the remote server # pear install HTTP_Upload Of course, there is a bounch of options and things the package installer can do, just read http://cvs.php.net/co.php/pearweb/doc/pear_package_manager.txt, for an introduction and how to make it work from CVS. We greatly appreciate testers! > >Still, beyond the installer, there isn't anything to compile yet, correct? > >I know that in the perl world, CPAN modules often come with a C version of > >certain functions for speed purposes. I did not find any C versions of > >Pear modules, though that's probably something you don't do unless really > >necessary. > > Right now there is no C code in PEAR, but this can change in the > future. If one wants to write (parts of) his PEAR code in C for > speed purpose, he can do so. > Well, there is indeed C code in PEAR, this is what PECL stands for, you know Martin :-) Tomas V.V.Cox

« previous php.pear.general (#1036) next »