this would conflict with PEAR's HTML_Template_Smarty should that ever
happen. As it stands, PEAR is the standard source of PEAR, and other
channels must take steps to ensure that they do not conflict with each
other. The best way to do this is to have a directory into which
everything is installed.
This makes sense. Maybe we should take this one step further and just include a Channels director in the top level so I could just:
require_once('Channels/Pearified/Smarty/Smarty.class.php');
That way I know it's a channel that I'm requiring.
PEAR packages can never depend on external channnels, this is a recipe
for disaster, as you note.
This needs to be in the CS *before* 1.4.0 is introduced. It should also be strictly enforced in the package upload utility.
--Joe
--
Joseph C. Stump
joe@joestump.net
http://www.joestump.net