Anton Aylward wrote:
I don't see a reason why we shouldn't have a tree for stuff that is specific to Suse.
I told the perl maintainer ages ago, that if they couldn't deal with the system perl being upgraded, then maybe they should have a dist-perl that is needed for crippled packages that can't be recompiled (like standard perl packages, as in CPAN), that can be recompiled for a new perl. The maintainer basically said that the system perl was for opensuse, and users were not suppose to upgrade it, even for bug-fixes that didn't change the call-API. I even contacted the perl devs who confirmed that minor version changes (5.20.0, 5.20.1, 5.20.2) in perl were "guaranteed" not to change the API, and modules for one minor version should "just work" in other minor versions. However, they don't on opensuse, because version numbers are hard coded into modules and perl causing wide spread breakage when perl is upgraded. If they had the modules build to allow recompilation as other perl-cpan modules, it wouldn't be an issue in most cases -- even when major versions changed. But trying to get some to change is like pulling teeth. Similar issue is the dependency hell, in many or most cases created by hard-linking libraries rather than doing run-time dynamic loading. Gvim has been that way (don't know about latest gvim). On windows (and on my machine at one point (not sure about now unless I test it!)), gvim tries to load python.so, perl.so, etc... and dynamically activates its ability to call those libs if they are present -- Versus -- opensuse just rolling over and dying. I usually tried to keep gvim on root, to help fix problems, but without /usr, (where all the interps were), it wouldn't start. Thing is, I needed gvim as an editor -- not as a script-host. Yet due to bad-SW-build practices, it wasn't usable. :-( A LOT of Opensuse products could be made alot more resilient by using run-time lib-loading and dynamic configuration. It's not a new idea. SGI did it 15-20 years ago, and dynamic GUI configuration was done based on available features on **Plato** back in the 70's! Do we ever learn? A large number of today's programmers didn't come out of a Computer Science curriculum and were self taught. While they know the most important and most needed stuff to stay employed, they usually don't care about "history" and thus are doomed to repeat mistakes and problems solved 40-50 years ago. :-( Thus SW doesn't really progress (and I've seen signs of it going *backward*). While CS used to design computer programs to be "user-friendly", now, because most programmers can't be bothered to learn how to do that, the demand is that *users*, be computer-adapted. Plegh. Even Gates idea of 3D desktop paradigms, intro'd as Vista and Win7 rolled out, have back-stepped, as Win10 went for a 1980's GUI. Everything is being dumbed down so users can be more easily controlled and doled out hand-helds w/all their info in the cloud that they pay monthly for -- w/no privacy. Lovely. I like the Win7 Aero, but it's not even an option above Win7. Bill G was so happy demonstrating some of its early features, and now...its being all rearchitected to run on the lowest end hardware. Plegh! ... I think I've gone off on tangents again....*sigh* -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org