Re: manual installation confusion
| From: | Stephen Musgrave | Date: | Thu, 29 Jan 2004 00:13:52 +0000 |
| Subject: | Re: manual installation confusion | ||
| References: | 1 | Groups: | php.pear.general |
| Request: | Send a blank email to pear-general+get-10415@lists.php.net to get a copy of this message | ||
i eventually figured this out, but it would be nice if the manual told the
reader that they would have to manually create the directory hierarchy. or
should i be posting this to the documentation list?
thanks: STEPHEN.
On 1/28/04 12:04 PM, "Stephen Musgrave" <stephen@musgrave.org> wrote:
>
> i'm confused by the documentation for the manual installation of PEAR.
>
> http://pear.php.net/manual/en/installation.manually.php
>
> i am trying to install Spreadsheet_Excel_Writer-0.6. when i follow the
> directions on this page, i have a directory structure that looks like so (I
> have changed the includes directory form the example in the documentation):
>
> /admin_includes/
> Spreadsheet_Excel_Writer-0.6/
> package.xml
> Spreadsheet_Excel_Writer-0.6/
> Writer.php
> Writer/
> BIFFwriter.php
> Format.php
> Parser.php
> Validator.php
> Workbook.php
> Worksheet.php
>
> I then add the ini_set line to my script:
>
> ini_set("include_path", $_SERVER['DOCUMENT_ROOT'] .
> '/admin_includes/PEAR' .
> PATH_SEPARATOR . ini_get("include_path"));
>
> I then require the Writer.php file in relation to the path directory:
>
> require_once('Spreadsheet_Excel_Writer-0.6/Spreadsheet_Excel_Writer-0.6/Writ
> er.php');
>
> I run the script and I get an error within Writer.php:
>
> PHP Fatal error: main(): Failed opening required
> 'Spreadsheet/Excel/Writer/Workbook.php'
> (include_path='/Users/stephenm/Sites/inductorsupply.com/htdocs/admin_include
> s:.:/usr/local/php/lib/php') in
> /Users/stephenm/Sites/inductorsupply.com/htdocs/admin_includes/Spreadsheet_E
> xcel_Writer-0.6/Spreadsheet_Excel_Writer-0.6/Writer.php on line 35
>
> It looks like it's looking in Spreadsheet/Excel/Writer/ for the Workbook
> file, but that directory structure does not exist by simply extracting the
> file as the documentation says. I would have to create that directory
> structure and reorganize the package manually. But when I do that, I get
> errors that other files can't be found.
>
> Is this right? Are there better instructions on how to go about a manual
> install? Am I missing something?
>
> Thanks,
>
> Stephen Musgrave
>
> ] stephen@musgrave.org
> ] http://stephen.musgrave.org/