[PEPr] Comment on RFC::Requiring E_STRICT Compatibility for New PEAR Packages

Justin Patrin (http://pear.php.net/user/justinpatrin) has commented on the proposal for RFC::Requiring E_STRICT Compatibility for New PEAR Packages. Comment: I'm a bit worried about this: "it has only E_STRICT-compatible required dependencies" While I understand that technically you can't run in E_STRICT mode with a non-E_STRICT file/package included the code in any package can be E_STRICT compliant without this requirement. Requiring package to only have E_STRICT dependencies means that we, collectively, have to start over from scratch for any dependencies we may need and/or convert existing packages to E_STRICT, causing a new major version with no real gain. Proposal information: http://pear.php.net/pepr/pepr-proposal-show.php?id=419 -- Sent by PEPr, the automatic proposal system at http://pear.php.net