[PEPr] Comment on RFC::Package naming, file naming and directory structure RFC

Daniel Convissor (http://pear.php.net/user/danielc) has commented on the proposal for RFC::Package naming, file naming and directory structure RFC. Comment: Combine the "Class structure" and "File structure" sections, particularly the examples. In those examples, put the path/file names in a fixed-width font. Under "Directory structure," "PHP files," what does "(or "" for non standard operating systems)" mean? Several comments regarding the "Other files" section... * Reword the sentence to say: "Files other than scripts must go into one of the following directories:" * Please clarify where examples should go. * It looks like you are talking about where files end up once installed. For example, "<installdir>/pear/docs/DB/STATUS." But when someone is writing a package, the working directory structure is different: "<cvsroot>/pear/DB/docs/STATUS." Or are you saying that the working directory structure must be "<cvsroot>/pear/DB/docs/DB/STATUS." If you mean the former, please clarifty the text. I hope you don't mean the latter, since that will add a whole heck of a lot of unnecessary directory levels. I still have reservations about the one class per file section, though I need to think about this some more before commenting. Proposal information: http://pear.php.net/pepr/pepr-proposal-show.php?id=55 -- Sent by PEPr, the automatic proposal system at http://pear.php.net