Re: [RFC_v3] Handling Backwards Compatibility in PEAR [hopefully the final draft]

From: Date: Thu, 25 Sep 2003 15:19:09 +0000
Subject: Re: [RFC_v3] Handling Backwards Compatibility in PEAR [hopefully the final draft]
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-22017@lists.php.net to get a copy of this message
Hi! Rob Hutton wrote:
1) I question why none of these people posted anything when this first was raised by a PEAR package that depended on the Log PEAR package which introduced a minor BC break in a non major release didn't get updated **IMEDIATELY** and someone asked about it. Greg, et. al., are not making up a solution that needs a problem, the problem already exists. Arguing whether the problem exists or not is pointless. It has been demonstrated. Please read the archives.
The change happened in Log 1.7.0 release. Whether the release is major is of course debatable. The change in question was in CVS for 2 months: http://cvs.php.net/diff.php/pear/Log/Log/file.php?login=2&r1=1.25&r2=1.26&ty=h The removed method was marked as public, but was not documented. The problem appeared when the author of a depending package made an explicit dependency on an older version of Log, instead of fixing his package to work with the most recent version (a one-line fix, as was found out later). So the problem exists, but the solution is far worse than the problem.

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