publicweb RFC

Hi, Here's an attempt at a preliminary RFC for the implementation of the publicweb role. The description of how the directory structure will look and other user-end considerations were discussed a few weeks ago. This is pre-code ideas on structuring the command so that it is practical. Once this sounds good, I will work on a new patch that implements the idea. 1. packages that contain files dedicated to use in a webserver should use the publicweb role for these files 2. the publicweb_dir config variable will default to data_dir for existing PEAR installations, unless the user manually sets publicweb_dir 3. publicweb_dir can contain an unlimited number of directories separated by the same delimiter used in include_path. Each directory will have the files installed into it by the installer [this will solve virtual hosting problem - input on chown problem is needed, chown to the owner of parent directory?] 4. on upgrade, the Installer will also check for any new directories in publicweb_dir for packages that are already installed, and copy files to the new directories [addition of new virtual hosts]. For this, the installer will need to add to the registry a list of packages that have any files with role="publicweb", and a list of those files. 5. addition of new directories to publicweb and deletion should happen through a new set of commands that perform the upgrade/uninstall automatically to directories. In other words, if a directory is added to the publicweb_dir, the files for existing packages are copied. If a directory is removed, the files are deleted. A few options should allow control over this similar to the --force option for install. pear add-webdir/pear delete-webdir ? 6. pear config-set publicweb_dir should automatically re-direct to the new functions with a notice to use the new functions This RFC solves two problems: -packages such as phpDocumentor and HTML_TreeMenu have static web files such as javascript files that require absolute URIs. This information is not calculable between packages, and makes dependencies virtually impossible between these two packages. The publicweb role would make these dependencies possible -PEAR installations on multi-user sites could have the publicweb files automatically installed to a subdirectory of their personal webspace. This would also be useful for sites with sub-domains Greg