Anders Johansson wrote:
[...]
And in some cases it will fail miserably. Not too many years ago, the YaST script syntax changed, and this caused any attempt to use System Update to upgrade to the next version to fail as soon as the new version of YaST got installed (it only read the new syntax, didn't understand the old, and everything went to pieces)
I don't know details about YaST repositories (or installation sources), but it seems as if the SuSE version is somehow encoded in the path and/or repository/package description. Would it be possible to check the running SuSE version against the new (online?) installation source to see whether the user is trying to do an entire "system upgrade" with the "System Update" module and, if yes, issue at least a warning that this is not the correct way...? Or could something like that be part of the "Installation Sources" module (warning message when user tries to import a repository that does not match the currently running SUSE version)? I don't know whether this is useful at all, it just came to my mind... I am sure that many people do not really understand the purpose of the "System Update" module. Cheers, Th.