09-14-2020, 02:00 PM
This is one of those hit-or-miss propositions.
Many Raspberry Pi OS (formerly known as Raspbian) package upgrades are benign; a few are disruptive. That's why some users have been able to report they have been doing it all the time without a problem. They just haven't hit one of the disruptive ones yet.
My guess is the easiest way to go wrong with confidence is to upgrade a system service and in the upgrade process accept a new, default configuration file rather than keep the one that moOde has customized in some way.
But the reason an upgrade causes moOde to fail doesn't really matter. Tim and his team test moOde as shipped and can't easily diagnose issues which arise because of changes.
The moOde release cycle is reasonably quick so you're never very far behind the curve.
Of course if you like living dangerously there's nothing to stop you.
Regards,
Kent
Many Raspberry Pi OS (formerly known as Raspbian) package upgrades are benign; a few are disruptive. That's why some users have been able to report they have been doing it all the time without a problem. They just haven't hit one of the disruptive ones yet.
My guess is the easiest way to go wrong with confidence is to upgrade a system service and in the upgrade process accept a new, default configuration file rather than keep the one that moOde has customized in some way.
But the reason an upgrade causes moOde to fail doesn't really matter. Tim and his team test moOde as shipped and can't easily diagnose issues which arise because of changes.
The moOde release cycle is reasonably quick so you're never very far behind the curve.
Of course if you like living dangerously there's nothing to stop you.
Regards,
Kent
