Feature requests for PEAR

Hi, I have a couple of ideas for the pear installer/packager. Maybe some one has already thought of this but here it comes. First I was thinking of crating a package without the files being on the same fs or folder as the package.xml <file role="php" baseinstalldir="Auth" name="Auth.php" file="http://www.someserver.com/Auth/Auth.php" /> or <file role="php" baseinstalldir="Auth" name="Auth.php" file="http://cvs.php.net/co.php/pear/Auth/Auth.php?login=2&r=HEAD" /> Side note: there is somthing which bothers me with the current installer, if you have name as a directory and file name="Test/Auth.php" the file would be installed in Auth/Test/Auth.php, now I would expect the name to be just the name of the file and not a path . Of cource other sourses should also be supported, cvs ftp webdav etc, this would make pear packages somthing like gentoo ebluilds, ie the package file is all you need to be able to build the package, the actuall files can reside someware on the network. The other feature which I would like to see in PEAR is scripts, preinstall, postinstall etc. Now these could be anything (bash,perl,tcl and of cource php), but since pear is also targeting Windows users which usually don't have these installed I think the most reasonable option would be to have these in php, plus php scripts can easily tap into the PEAR api and do some cool stuff. Now the last thing which I want to bring up is installation of Applications. How do we install applications with pear, I know the topic has been touched a coule of times before and I remember stig mentioning somthing about it. it is also possible to ovveride the install dir on the command line with #pear -D php_dir=/www/htdocs/someapp install SomeApp.tgz but this would make the package not register as installed in pear and makes mantenance a bit hard. Am sure there is work in this direction but I have no idea where to look, I have a small play project with which am playing and I would like to have the option to deploy it with PEAR, am sure some debugging and testing on this would not hurt. Yavor