Re: Problems using PhpDocumentor

From: Date: Wed, 18 Feb 2004 18:17:20 +0000
Subject: Re: Problems using PhpDocumentor
References: 1  Groups: php.pear.dev php.pear.general 
Request: Send a blank email to pear-dev+get-25695@lists.php.net to get a copy of this message
On 18 Feb 2004 at 13:13, Greg Beaver wrote: > Even with the new web_dir role, people would still need to configure > the proper location themselves - there's no way around the extra work > required. The true solution for applications is not a generic role, > but instead a plugin system that allows a custom role to be set up > with user interaction at install-time, in my opinion. This would > allow database setup, for instance, with files that have role="mysql" > role="mssql" etc. which are .sql, but should be input into the > database instead of just saved to disk. Or, modifications to an > apache .conf, or php.ini, which is another complex installation task > that many applications will need. Well, think of a single-http-system. There you can pretty well install into the web_dir. And if no web_dir is set at all we might want to ask the user in the installer where the files should go. You could also create a subdirectory "pear" in every virtual host that's symlinked to the web_dir. Having also automatic database installs etc. might be a really nice solution. However, I don't think we can get it work smoothly in every situation. But I believe the web_dir might have future. Hmm, since I seem to be the only one (+Greg) who feels like this, maybe let's stop that discussion. If not, please speak up! Stefan

« previous php.pear.dev (#25695) next »