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

From:	Greg Beaver	Date:	Thu, 18 Sep 2003 00:30:11 +0000
Subject:	Re: [RFC] BC breakage in PEAR - how to handle it properly
References:	1 2 3	Groups:	php.pear.dev
Request:	Send a blank email to pear-dev+get-21673@lists.php.net to get a copy of this message

Hi Alan Alan Knowles wrote:

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

Absolutely - this should be explicit in the standard, I think.

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..

Wouldn't this introduce a paradoxical dependency on version 1.x in version 2.x? I think this is a bad idea, even if it seems to save a little disk space

Now to solve the subpackage issues :)

Yes :) Greg