RE: [PEAR-DEV] PEAR packages including files accessible through w eb

Yup, there was a talk about having a new role for files which should be put in a web-server accessible directory. It would be a good step for application installation as apps often need files in and out of the web structure. AFAIK it is planned to integrate, don't know when though. Bare with me because I may be wrong ;) Arnaud. > Sorry if this has been hashed out and I didn't notice. > > Some PEAR packages include files that are meant to be accessible > through a web server. An example is HTML_TreeMenu: this > package includes > quite a few images and other stuff that has to be put in an area > accessible through a web server, but they're still installed > /usr/local/lib/php/HTML. I dare to say /usr/local/lib/php is > not usually > visible through web, nor should it be. > > How about putting PEAR programs in ${PREFIX}/lib/php and > files meant to > be accessed through web in ${PREFIX}/share/php? The structure of the > latter would mirror that of the former, and this could help > establishing > a standard web-accessible path for PEAR files. PEAR programs > that would > need to put links to externally visible media (.js files, > images, etc.) > could quite safely use, say, "/pear/HTML/TreeMenu/...". > > What do you think? > > -- > If you cc me or remove the list(s) completely I'll most likely ignore > your message. see > http://www.eyrie.org./~eagle/faqs/questions.html > > -- > PEAR Development Mailing List (http://pear.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php >