Page 1 of 1

PEAR - Weird Includes Directory Configuration

Posted: Fri Mar 25, 2005 4:02 pm
by Ambush Commander
After figuring out exactly how ini_set worked for include_path, I set off to get some PEAR libraries to put into my /libs directory. The PEAR::Auth library was first.

But after playing around a bit, I realized that if I was going to use PEAR, I needed the root PEAR class. So I downloaded that too.

And then I got completely confuzzled with the directory structure.

Inside the PEAR directory, you have a bunch of folders, and then PEAR.php, System.php, template.spec and package.dtd. Do I copy these files and the folders into my base_include directory? Which ones do I need and which ones do I not (for instance, /scripts contains a .bat file. Do I need that?)

Taking a look back at the XML package file, it looks like the PEAR class also has it's own set of dependencies and it looks like every file is necessary.

And then I look at Auth and I go "wtf"? It's like, I'm going to have to manually parse the <filelist> element, making sure every file goes where it belongs because for Auth I can't even copy and paste: I have to set up the directory structure myself!

WTF!

I can see why they provided a PEAR installer. In fact, by typing this question, I've solved my problem (well, at least, now I know how to install the packages)! But...

Is there a better way??? (only for manual installation)