Home » Authentication » Auth » Bug #2060
Invalid directory structure in Auth 1.3 r2 tarball
Details
| Submitted | 2004-08-05 04:32 UTC |
|---|---|
| From | chris at nullcode dot org |
| Assigned | aashley |
| Status | Wont fix |
| Package | Auth |
| PHP Version | Irrelevant |
| Roadmaps | (Not assigned) |
Comments
[2004-08-05 04:32 UTC] chris at nullcode dot org
Description:
------------
When the Auth-1.3.0r2.tgz is extracted it has the following directory structure:
.:
Auth Auth.php Container Container.php Frontend README.Auth tests
./Auth:
Auth.php Controller.php
./Container:
DB.php File.php LDAP.php MDB2.php POP3.php SMBPasswd.php vpopmail.php
DBLite.php IMAP.php MDB.php PEAR.php RADIUS.php SOAP.php
./Frontend:
Html.php md5.js
However, for Auth to function correctly, Container/, Container.php and Frontend/ must be subdirectories of Auth/. If you attempt to extract this in your PEAR directory and use it you will get the expected error when Auth tries to include Container.php or files from Frontend. It would be nice if the upstream tarball reflected the correct necessary directory structure of the module.
Reproduce code:
---------------
For example,
Auth.php:342
require_once('Auth/Container/' . $driver . '.php');
-and-
Auth.php:427
include_once('Auth/Frontend/Html.php');
[2006-02-21 06:09 UTC] aashley at php dot net
Not going to fix this right now, involves moving stuff in CVS which is a nightmare, bring on subversion please.
Anyway the tarballs are designed to be installed by the PEAR installer it takes care of placing all the files in the correct locations and making sure dependancies are satisfied. If you are installing into a shared environment take a look at PEAR's new ftp install feature where a locally run PEAR installer can install packages into a directory over FTP.