1.
Change the PEAR CVS directory structure to reflect the PEAR user
directory structure completly. You havent got a rat's chance in hell of getting that through - it make cvs karma imposible, and makes package.xml's a nighmare :)
- I'd remove it from the RFC..
2.
Simply use ini_set('include_path', "/your/cvs/pear/Image_Text:" .
ini_get('include_path')); to require one or more packages from their CVS
directory (for multiple packages you have to add multiple strings before
the old include_path).
Actually you can still soft-link this in the same maner you would in the old way...
Cons:
- Slight WTF factor when browsing cvs.php.net/pear (on packages that use it..)
- Long_Package_Names will have to look a long way down for the actual files.. in CVS..
Pros:
- Very easy developement.
- Very comfortable developement.
- No per-package influence on include basis.
These seem a little abstract (even misleading)
- easier for beginners to understand directory structure
- easier for windows users who can not use softlinks.
The boat is still out on this one. - but if you could tidy up the RFC and remove 1).. it may help to move it forward..
Regards
Alan
--
Can you help out?
Need Consulting Services or Know of a Job?
http://www.akbkhome.com