Cristian Rodríguez wrote:
El 11/02/13 15:26, Linda Walsh escribió:
But that's why I've had all theseproblems ... no way to get from here to there...
We have explained to you ad-nauseum that there is nothing wrong with libc, whose compatibility promise is been kept under the same constrains for a decade or more.
Components other than libc have their own binary compatibility policies if any. those who dont publish any document stating a policy on this matter *must* me assumed like there is none and that ABI/API may change at will.
YAST belongs to openSuSE.. I wanted to upgrade my perl, but yast in 12.1 claims it requires perl5.14 and won't work unless I downgrade. This never used to be the case. Did OpenSuSE change policy to lock all of their own apps into each version so no versions can be used? That would be a really bad policy -- since, more than once, on upgrade, I've found a new version of "X" either doesn't work for me, or is going to take some time and effort to upgrade (samba 3.5.x->3.6.x required remaking the user database -- have seen that on the samba list from others as well). Sometimes it's samba, sometimes, it's ng-syslog, nearly every upgrade has had some issues. Gvim -- was another one -- built specifically to perl-5.14.so. But if you build it as generic "perl.so", then gvim works fine with multiple versions. Same applied for python and and another script language -- I ran into some issue with ruby (which I found a bug report on, and a workaround, but was too complicated and I was in rush, so built w/o ruby... The rest are loaded at run time -- not load time. So if they are not on the machine, at least the person can run the editor. But more importantly -- the way it is in the distro -- you can't upgrade perl. Suse had never locked specific versions of tools before 12.1, but did in 12.1 -- nearly every binary is linked with every other binary by name+version -- not just name as it used to be. Many (Most?) RPM's have had "pre-reqs" changed from some *minimum* version of a package to *exact equality*. As someone who constantly is upgrading software, having everything locked together, really is broken. Can this be fixed (obviously not overnight, but some policy needs to be reverted)... Neither the yast nor the gvim changes come from upstream -- they are suse changes. . -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org