Re: Re: why bloated packages are bad (acaseforsplittingup large packages)

Hi Lukas Smith! On 08/15/05 20:58 you wrote: >> There is a new tag provided (<compatible>) which has a large potential >> to solve this issue. Quoting from an email posted by Greg yesterday: > I got that one, but I just dont see what it solves. I mean will the > minor release then state its not compatible (untested) with PEAR? Then > you obviously cant upgrade to that version and therefore the entire > advantage of releasing that package update becomes moot. I think Greg stated the way it will work very clearly: - Package A depends on B. - B upgrades it's version. - User tries upgrade, which will throw a warning about maybe incompatible versions. - PEAR developers and experienced users can test if BC was broken with forcing PEAR to upgrade. - If all issues are fixed B releases another upgrade including <compatible>-tag OR package A updates stating it can work with new version of B. - PEAR will allow upgrade for users. Hope that explains the intensio of <compatible> better. Regards, Toby -- Tobias Schlitt - Zend Certified Engineer GPG Key: 0xA6529579 a passion for php http://www.schlitt.info Like to say "thank you"? - http://pear.php.net/wishlist.php/toby