PEAR packages including files accessible through web

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