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

Davey Shafik (http://pear.php.net/user/davey) has commented on the proposal for RFC::Package naming, file naming and directory structure RFC. Comment: I think the best way to handle classes Vs files after reading the thread about compiler caches and such on pear-dev/php-internals is that PUBLIC classes, i.e those the use will actually require to use to package, need to be 1 Class/File for ease of inclusion by the user, others can be stored as the developers see's fit - if a class is then moved to being a public class, it can be moved into its own file.... This seems to be the best solution I can come up with... Additionally, the sentence: "Coming packages have to implement all of the above described rules." in the "Update non-conform packages according to the defined rules." section needs to be re-worded, does it mean packages from say Horde? or new packages all-together? you should change "Coming" to "Migrating" or "New" respectively for these two things... if you mean both, "New/Migrating" should be used :) In the "Scope" section, you need to change "Sense of this proposal is to" to just "This propososal is to" - Davey 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