https://bugzilla.novell.com/show_bug.cgi?id=804070
https://bugzilla.novell.com/show_bug.cgi?id=804070#c17
L. A. Walsh changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
--- Comment #17 from L. A. Walsh 2013-03-05 11:49:41 PST ---
The advice was that suse doesn't need to arbitrarily reduce functionality --
there is no engineering reason to do so.
There is no difference in minor revisions, and if a major revision occurs,
allowing for a 'recompile' of the affected modules *should* be allowed.
But finally -- I mentioned that my perl scripts do the daily maintenance on my
system and when I change perl, that needs to be the one that is picked up by
default by root and other users.
It's suse that has changed the policy to *need* a specific version -- this
wasn't the case before 12.1.
If suse needs a particular version -- as I have said before, they should keep
their own copy in a private directory and leave the user's system copy to
the user.
Suse cannot justify forcing per-version tying, as the perl people claim binary
API compat -- and even between major versions, a simple recompile of the
affected modules should be trivial.
It was also suggested I look for the perl version I wanted on the build-farm --
I did. There was no build of perl5.16.[012] for suse 12.1.
I did read their suggestions and responded as to what would work, what did work
and why. Resolved in this case would be suse fixing the problem. Not closing
this as invalid.
Suse's not following standard policy puts this in suse's court as a valid bug.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.