Re: semi-RFC: new file role needed: docroot
| From: | Pierre-Alain Joye | Date: | Fri, 25 Jul 2003 22:44:03 +0000 |
| Subject: | Re: semi-RFC: new file role needed: docroot | ||
| References: | 1 | Groups: | php.pear.dev php.pear.general |
| Request: | Send a blank email to pear-dev+get-18721@lists.php.net to get a copy of this message | ||
On Fri, 25 Jul 2003 18:33:57 -0400
Greg Beaver <greg@chiaraquartet.net> wrote:
> Hi,
>
> I've been investigating the sources for PEAR, and an initial scan says
>
> it won't be easy to do, but that it will be possible to add a new
<snip>
> post-install or post-install-script, which specifies that the script
> should be run after installation. The zzoss installer has something
> like this, I believe, perhaps Sandro can comment.
I like the idea. However I would prefer to have multiple doc_root
support. The DocRoots are stored in the global config or user config.
While installing, pear can automatically loops inside the DocRoots and
copy the files there (and/or link?). Whether it does it automatically
should be define in a config option.
Before doing that, we have to define naming and directory structure to
skip conflicts. I propose lowcase names for the files/folders using the
exact same trees as pear itself. ie:
docroot:
|__pear
|__html
|__javascript
|__Perm
or the same structure as used in data:
docroot #1:
|____html_javascript
pierre