[PEPr] Comment on RFC::Package naming, file naming and directory structure RFC
| From: | PEPr | Date: | Sat, 22 May 2004 14:19:51 +0000 |
| Subject: | [PEPr] Comment on RFC::Package naming, file naming and directory structure RFC | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-29557@lists.php.net to get a copy of this message | ||
Stefan Neufeind (http://pear.php.net/user/neufeind) has commented on the proposal for RFC::Package
naming, file naming and directory structure RFC.
Comment:
The RFC is fine from my side. I wondered if the demand for
"Current packages are in general required to upgrade to get conformity." is really
necessary and how it should be achieved - but if this sentence should stay I can live with it since
you also mention that BC has priority over this regulation.
Would this mean that upon a new major version a package not fully according to those standards needs
to be renamed? Are there candidates?
One minor thing under "Package classification":
Does "size" really matter? :-) You're possibly thinking about things like Cache_Lite.
But wouldn't this classification go under "functionality"? Imho size sounds a bit
strange in this list.
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