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

Alexey Borzov (http://pear.php.net/user/avb) has commented on the proposal for RFC::Package naming, file naming and directory structure RFC. Comment: Definitely looks better than the first version! Still has some problems, though: *Class naming* Does this imply that every package should have only one "main class"/"base class"? If yes, this should be _explicitly_ mentioned, I think. *File naming and structure/Exception* "Either way every class that maybe be instantiated directly should reside in its own file." I suggest re-wording it as "every class that can be used separately". E.g. DB_result (from DB) or HTTP_Response (from HTTP_Request) can be instantiated directly, but it makes no sense to use them without other package's classes. *Directory structure* This part makes no sense in its current form and should probably be removed. PEAR installer already installs the files in such a way if they have proper roles in package.xml, and I think this RFC does not need to cover writing package description files. 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