Directory layout of package

Hi QA peepz, A question about 'PEAR Standard' directory layouts for extreme cases: Currently, the structure of PEAR_Frontend_Web, when installed, is the following: PEAR/WebInstaller.php PEAR/Frontend/Web.php PEAR/Frontend/Web/<all data files> The 'WebInstaller.php' file handles the _GET and _POST requests and translates this into PEAR_Command actions, which call the frontend implementation (Frontend/Web.php) Problems I have now: * WebInstaller.php is a very unclear and non-standard name * all data files are in Frontend/Web/, I whish to create a new PHP file, but I don't want to put it between all the data. I was thinking of the following as a replacement layout: /PEAR/Frontend_Web.php /PEAR/Frontend/Web.php /PEAR/Frontend/Web/Docviewer.php (the new php file) /PEAR/Frontend/Web/data/<all data files> My 2 questions for QA: 1) First and far mostly: Is it OK to do file renames, or should this be avoided (as I think version information in CVS is lost when doing a rename?) [note that its a stability-alpha package and that I rewrote most code for its 0.6 release] 2) Is Frontend_Web.php in this case a good name, or is it better to take something like Frontend_Web_Handler.php to avoid confusion on what file does what. Thanks and Greetings, Tias