El 09/06/13 18:25, Linda Walsh escribió:
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.
No, it is not broken, it is working exactly as expected,wanted and designed.
how about compat with previous version of suse where it wasn't done OR following the same rules as with ruby or python??
Nope, we have to keep down the number of supported scenarios and that goes this way: -User does a clean install for example openSUSE 12.3 (can be whatever version, I choose 12.3 as an example only) - openSUSE 12.3 is unlikely to change its perl version for its lifetime, but if it does, all packages will be updated and published at the same time. - User wants to upgrade to 12.3 + 1 , before upgrade, all dependencies of all installed packages must be satisfied so the upgrade path is clean an works, no mixes between old and new versions, if there is dependency problem, warn or abort update. Development resources are a limited asset and number of things that can go wrong in the case you want to support a custom perl version are almost impossible to manage. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org