![](https://seccdn.libravatar.org/avatar/cabdbf4d350ab6a15265803acab1634d.jpg?s=120&d=mm&r=g)
On 01/05/2020 09:58, Patrick Shanahan wrote:
* Anton Aylward <opensuse@antonaylward.com> [05-01-20 08:46]: [...]
I don't have to move from 15.1 to 15.2 to drown in .rpmnew files where the new 'upgrades' have, for example, dot-conf files, that come into conflict with my updates.
But WTF, I'm lecturing to the choir.
This is why I dread upgrades. They blow apart my carefully and carefully considered configured system.
Jim Dandy to the rescue
er s/Jim Dandy/Tumbleweed
but even Tumbleweed does not endure forever, accumulation of cruft and "old standards" still eventually require/call for re-installation. I got six years before succumbing the last time.
Fair enough. Tumbleweed is one form of 'incrementalism', and a pretty aggressive one at that. My use of kernel_Stable is a focused for of aggressive incrementalism. It would have addressed the OP's problem and is quite compatible with all the 15.1. With nvidia? I can't say based on my own experience; I don't run nvidia; i run intel and my experimental boards run AMD. I suppose running 'zypper up' daily is another form of 'soft' incrementalism. Yes i do that and yes I'd recommend looking at it. It may not be as dramatic as Tumbleweed in it's completeness, it may not last for the six years, but once you have a stable system, incrementalism is less disruptive than the 'catastrophism' of a complete upgrade. if you google for 'gradualism vs catastrophism' you find this to be an ancient debating issue in both geomorphology and genetics. Both areas have seen pretty vociferous "discussion" on the matter, so I'd expect nothing gentle here on the matter :-) -- It isn't that they can't see the solution. It's that they can't see the problem. - G. K. Chesterton -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org