BTW, a re-flash or re-install of the whole norns system is rarely needed. (Not just for mods problems, but in general.) The idea of doing a fresh install is I think a hangover from the days of operating systems and applications that did not have proper software management. I’m thinking of Windows and Mac OS back in the day, and the very earliest days of Linux. Norns does not scribble over itself all the time like those old OSes did, so corruption of the base system is almost not a consideration.
Scripts and mods can get themselves into a bad state, though. From reading around lines, it seems that scripts get in trouble sometimes when they store state in dust/data or when they have corrupt presets. Those scripts sometimes need to have their data directory deleted. Some scripts and mods may have dependencies on other scripts or mods, or they might have extra install steps. Those scripts and mods can end up in a state where they have not been completely installed, and cannot continue. In those cases, the entire script or mod may need to be deleted and re-installed. But still, the norns system itself should not need to be touched. I think your issue with n.b. falls into this category.
There are a very small number of scripts or mods that install their own software alonside norns, or modify fundamental parts of the system that are not accessible through the usual norns scripting interfaces. I think Orac/sidekick, zxvcbn and warmreload are examples of scripts that do this. Maybe also connect-opz, connecto and autojack? If one of these scripts has a problem, that could cause issues for the rest of norns and possibly require a full re-install. (The issue here is that norns scripts commonly have instructions for installation, but no instructions for removal. If a script is self-contained, there is no need for such instructions because it is obvious: just delete the directory from dust/code. But if a script is not self-contained, it can be hard to figure out how to remove it cleanly. That is when you might have to fall back on a fresh install of norns.)
It would be nice if we had an index of scripts that reach out beyond the normal norns interfaces. Users would know that they need to do extensive surgery only if one of those scripts is involved. For everything else, just removing the script at hand or clearing its data would be enough.
(It would be even nicer if there were a rudimentary package management or dependency management system. But it is not simple to solve that problem without imposing a burden on script authors and system maintainers.)
2 Likes
