Re: Re: Fwd: PEAR file-hierarchy

Lukas Smith wrote: [snip stuff about install-as needed for role="doc"]

yup seems to me like something that needs to be fixed inside the installer

I don't think there is a generic fix for this. Remember - people outside of PEAR are/will be using the packager for their own packages. Often, they will not follow the directory convention we have set up. The only truly reliable method is an explicit fix for a directory. In other words <dir install-role="doc" name="docs"> <file name="somefile.html"/> </dir> This would tell the installer that docs is the base install dir for all role="doc", and so should be removed on install. Package/somefile.html instead of Package/docs/somefile.html Here is the reasoning. phpDocumentor, for example, has a README file and an INSTALL file that are always in the root php directory. How could the installer determine, generically, which directory it should go in? If it always simply removes one level then they would be installed in the parent directory of PhpDocumentor, which is "a bad thing(tm)" I would actually like to see the roles handled much less rigidly. The switch statement in PEAR_Installer::_installFile() is not nearly powerful enough to handle complex situations such as doc files that really belong with PHP files (like README), or other common situations such as the difference between readable and writeable data. This, however, is most definitely a feature for PEAR 1.5 or PEAR 2.0. Right now, channels is absolute top priority. Everything else will have to wait, so that there is some semblance of quality control over the core, otherwise we'll have a big disaster with the next minor release :). The code is finished but not fully tested, and so it makes little sense to make it publicly available until all of the obvious kinks have been debugged. Greg