Re: Re: why bloated packages are bad (acaseforsplitting up large packages)

Hi Lukas Smith! On 08/15/05 18:21 you wrote: >> Can you understand that there is code regarding dependencies in PEAR >> 1.4.0 >> that addresses the concerns you have with the way dependencies were >> problematic in the past? > I am not aware of anything in PEAR 1.4 to protect us from accidentatly > BC breaking releases in dependencies. There is a new tag provided (<compatible>) which has a large potential to solve this issue. Quoting from an email posted by Greg yesterday: > The *only* thing the PEAR installer does that is better than simple > unzip-and-install is manage dependencies. In the past versions of PEAR, > it did this rather terribly, allowing upgrades to BC-breaking releases > of dependencies such as Console_Getopt and so on. This problem is fixed > with the <compatible> tag. Releases can be made of a package that will > NOT automatically be upgraded by any user, allowing testing and proper > configuring/fixing prior to making the dependency compatible. > The act of avoiding dependencies results in bloated, ridiculously large > extraneous stuff in packages, which also defeats the primary strength of > PEAR: the ability to quickly release a fixed package without having to > redundantly release everything in the package. 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