Cristian Rodríguez wrote:
so if perl version changes, let's say to 5.16.4 , all packages that depend on it are automatically rebuilt, their dependencies updated etc.
Why? If they work with 5.16.3 5.16.2 5.16.1 or 5.16.0, it should work with 5.16.4 It's just like the glibc -- a newer version will work with the older but for perl -- only guaranteed within a major version. So 5.18 -- not guaranteed. Might work but might not. Perl has always had the option to build and include libraries from the previous versions. Suse has notably broken minor version compatibility.
If not, perl 5.16.4 will be published to users but not those who depend on it, then at startup, programs will fail to fin
/usr/lib/perl5/5.16.2/x86_64-linux-thread-multi/CORE/libperl.so that is no longer there.
They shouldn't fail to find it if perl was built correctly. But you are saying you don't know how to build it such that it would work? The
You also haven't explained why the same wouldn't be true for ruby or python.
rpm --eval %py_requires --> for python
--- libpython handles libpython2_7-1_0-2.7.3 2.7.1.0 - 2.7.3 So why not perl handling 5.16.0 - 5.16.3?
rpm --eval %rb19_ver --> for ruby
--- Better -- ruby only requires the perl equiv of 5.16.X... Why not have perl requires only look at the major version like ruby? Bo
This is the expected behavior from the distribution POV;
---- That ruby supports multiple minor releases, that ruby ignores minor releases and perl fails over minor releases? What distribution could justify such when perl's policy is compat within a major release?
there is nothing wrong it so it will not be changed unless you have a very compelling reason to do so (no, "I build my own packages" is not a compelling reason)
how about compat with previous version of suse where it wasn't done OR following the same rules as with ruby or python?? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org