Re: Re: semi-RFC: new file role needed: docroot

Greg Beaver wrote:

Another solution for a centralized pear with multiple users would be to allow the publicweb_dir config variable to be an array of paths. Then, each time a new package is installed or upgraded, it would install to all paths. Obviously, this would require a bit of finagling through scripting to add directories, but something like that shouldn't be generic anyways. This option might be useful for the role="data" as well. The installer would only need to add a check for the type of the config variable.

I think the problem is a problem of understanding. (or using a tool which wasn't designed for this problem) The PPM is dedicated to maintaining a code repository on a computer, which means that 'root' creates an central dir readable by all other (web-) user, where libraries reside. But an application is user specific, not computer specific. Each application should work independent of other user applications. Application managment can't be centralized until the application itself contains a kind of user/vhost managment. (a little bit like ie. phpMySQLAdmin) I see two ideas for solving this problem: 1. add user management to PPM, ie: pear -u am21525 -p secret install myApp 2. keep the PPM as is and add a PAI (PEAR Application Installer), the PAI would be installed in each user home dir and allows user-specific settings and app installation (and an custom installation of PEAR too)