Re: Breaking BC / Changing API / Deprecating

Joe Stump wrote: > Guys, > > I've heard from the QA team that you can't break backwards > compatibility without creating an entirely new package (ie. Foo_Bar - > > Foo_Bar2). Or change the API without doing the same. Does this simply > sound retarded to anyone else? Isn't this what version numbers are for? The RFC discussion is here: http://news.php.net/php.pear.dev/21665 It should address all of your concerns. The question is not similar to kernel function names, but to dynamic library versions. From my /usr/lib: libstdc++.so.2.7 -> libstdc++.so.2.7.2.8 libstdc++.so.2.7.2 -> libstdc++.so.2.7.2.8 libstdc++.so.2.7.2.8 libstdc++.so.2.8 -> libstdc++.so.2.8.0 libstdc++.so.2.8.0 libstdc++.so.2.9 -> libstdc++.so.2.9.0 libstdc++.so.2.9.0 you'll see I have installed several incompatible versions of the same library. This ability is essential to gradual package migration, and is what the naming scheme aims at. Cheers, -- Sérgio Carvalho