Re: Proposal for Package naming : updating existing non-conform packages

Cipriano Groenendal wrote:

In fact, I would like to upload a new release for the Var_Dump class (PHP category), following the above rules : the package was previously released

under

the (non-conform) name "Var_Dump", but to match the defined rules in this

RFC,

the package should be named "PHP_Var_Dump".

This would result in a major BC, would it not? With a different package name, a different classname, or different filenames, none of the old scripts still using Var_Dump would work anymore. Changing any of these would thus result in a major BC, and since Var_Dump is already at state Stable, you'd have to release a new major version(PHP_Var_Dump2). Also, with most rules like this, the older packages NEED NOT conform to it, if changing it would break BC. Where possible, however, they SHOULD try and follow these rules. New packages, and additions to existing packages should ofcourse follow these rules. Cipri

Shouldn't it be PHP_VarDump like GTK_VarDump ? - Davey