Re: [RFC] BC breakage in PEAR - how to handle it properly
| From: | Greg Beaver | Date: | Thu, 18 Sep 2003 05:22:42 +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-21685@lists.php.net to get a copy of this message | ||
Marshall Roch wrote:
Greg Beaver wrote:A look at CPAN's docs for developers doesn't mention any restrictions on version aside from properly using the $VERSION variable at the start of your files. A peek at DBI's package page describes changes from an earlier version, and it looks like BC is an individual author's choice. Their only recommendation is to update source often to get bugfixes. It might be good to check out debian and perhaps RedHat rpm to see what they do. My experience with them is that dependencies are version-specific (future dependencies are not allowed at all) I think we may be treading new territory here :). GregProblem: BC breakage in PEAR has not been addressed. If one package depends on version 2.x of a package, and another depends on version 1.x, one package loses in the end. version 1.x can't be installed with version 2.x.Just out of curiosity, how does CPAN (or other similar projects) handle this, and does it have any major problems?