Re: Breaking BC / Changing API / Deprecating

Joe Stump wrote: >> >> The Linux kernel is an etirely different beast. First of all you have >> to know (somewhat) what you're doing to upgrade to a new one. It's not >> as simple as "pear upgrade-all". Second, the kernel's API doesn't >> really change. At least not the exposed API. The internal API can >> change in all sorts of ways and it won't affect programs which run on >> top of it. If an external change is made a huge deal is made out of >> it. > > > Have you used make-kpkg under Debian? Also, you're basically saying > that since PEAR users are too stupid to understand that sometimes API's > change with major point releases that we have to insulate them with > Foo_Bar, Foo_Bar2, Foo_Bar3, Foo_Bar4, etc. Not to mention things get > really hairy when you have packages A and B relying on Foo_Bar, while > packages B and C rely on Foo_Bar2 and then package D relies on > Foo_Bar4. I now have 3 different Foo_Bar packages installed, each with > slightly (not drastically) different API's. The problem is this: Have a user needing packages X, Y and Z. X has two versions with incompatible APIs, v1.0 and v2.0. Both Y and Z depend on X. Y depends on X version 1. Z depends on X version 2. How can you install all the packages? Cheers, -- Sérgio Carvalho