Re: [RFC] BC breakage in PEAR - how to handle it properly

From: Date: Thu, 18 Sep 2003 00:25:38 +0000
Subject: Re: [RFC] BC breakage in PEAR - how to handle it properly
References: 1 2  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-21671@lists.php.net to get a copy of this message
Package Foo version 1.x will be named "Foo" Package Foo version 2.x will be named "Foo2" Package Foo version 3.x will be named "Foo3"
This looks/sounds like a workable, attractive plan to me..
Package Foo version 1.x
Foo.php Foo/Supporting/FileOne.php Foo/Supporting/FileTwo.php
I presume that was
Foo/Suporting.php = Foo_Supporting Foo/Supporting/FileOne.php = Foo_Supporting_FileOne
Foo.php Foo2.php Foo/Supporting/FileOne.php Foo/Supporting/FileTwo.php Foo2/Supporting/FileOne.php Foo2/Supporting/FileTwo.php
Whether a package installs/uses old files should really be up to the maintainer.. (as long as BC is kept on the old files) however It's probably likely that giving the API change in the parent.. - that the child files will probably have to change anyway.. Now to solve the subpackage issues :) Regards Alan -- Can you help out? Need Consulting Services or Know of a Job? http://www.akbkhome.com

« previous php.pear.dev (#21671) next »