Re: PEAR 1.3

Hi, Before moving ahead with the patch we provided for installing phpDocumentor 1.2.2, the question of what to do with multiple hosting needs to be resolved. If I can quote myself from a back-channel message to Pierre: The main problem I can see with the publicweb role now is that it only allows 1 directory for installation. To add the ability to install in multiple locations would in fact be an interesting idea, perhaps something that should be implemented for all of the roles, but in my initial attempts to code something like this just for the publicweb role, I just don't think it's possible. The best solution I see is to keep the current publicweb patch, and instead patch the --installroot option so that many directories can be passed in. Alternately, there could be a new config value that is an array of paths (adding an array value to config would not be hard to do, I wrote some code that would do that, and people can pass in paths with spaces using "quotes" around them). This way, a global server could install local copies of PEAR code for every user in their own directory, without needing to add any system paths to the PHP include_path. This will also require a change to the registry, but I think saving the installroot, and catching any change to installroot so uninstallation/installation can happen is the way to go. I don't see this being an issue for the typical single-user installation, however. The patch I've provided works brilliantly in that situation. I also have patches to go-pear and the web installer that I submitted back in mid-July as well, that prompt for the new publicweb_dir directory on installation. Incidentally, back in the day of voting on the name, there were 6 votes for publicweb, and 1 vote for htdocs. This was unofficial, obviously, but that's why I used publicweb. It's no problem to change it and release 1.2.2pl1 with a revised package.xml for phpDocumentor. I think most users will be more familiar with the public_html directory, perhaps we should simply call it public_html or www? I have no strong feelings about the name. Greg Stefan Neufeind wrote:

On 19 Aug 2003 at 20:45, Martin Jansen wrote:

now that PEAR 1.2,1 has been released, I guess we should head towards version 1.3 including Greg's publicweb patch [1]: IMO the patch is fine, but I would like to rename the role to "htdocs", as this seems to be the most common expression. (IIRC someone else also stated that.) Comments? [1] http://phpdoc.org/patch/publicweb-PEAR-1.2.1.patch.txt

Well, you're right that htdocs is more familiar to the "Apache- speaking" people :-) But is this a real necessity? Maybe just "web" would also be okay, since there is no "privateweb" as far as I know in this case. Hmm ... maybe just "web" - or "htdocs" is also fine with me. I like the idea / patch - no matter for which publicweb/web/htdocs we might decide. Hmm ... just web?!? *g* By the way: If you're having virtual hosts - what would your "publicweb" directory be?!? :-)) Stefan