https://bugzilla.novell.com/show_bug.cgi?id=223524 ------- Comment #36 from koenig@linux.de 2006-11-29 11:27 MST ------- (In reply to comment #31)
Can we forsee that this will not break a later update under all circumstances?
thinking a bit harder I always can imagine some brain dead mechanisms in the next update which will break with whatever you ask me to break ;-) what I can forsee for sure: there are a some issues being mentioned here which _will_ break without such compatibility adds. and breaking stuff in 10.2 and only offering a fix in 10.3 _many_ months later for sure will make more than annoy some SUSE admins/users.
If we ship this it may create a support issue in the future.
if you don't ship this you'll have some update support issues in the near future. ok, your support crew will just answer "hey, the broken script is yours and not ours, so just go away and fix it yourself" but the reputation of SUSE/Novell won't increase with such behaviour...
If for instance you cannot remove the directory because it's not empty there may be a binary with the same name in the other directory. In this case if you move the directory and link you may create a validation error or an uninstall may later catch the wrong file. If such duplicates exist (and I think in the past they did to destinguish between X and non-X aware versions of an application) it may not be save to monkey with the directory at all - without risking the integrity of the installation. That's why I don't like to ship such a script.
vaild point. two thoughts (no solution:) about this: - the admin must be told (via email, popup window, ...) about these duplicate images & directory renaming. so (s)he knows and shall resolve that confilcts _before_ the next update (say 10.3 or whatever) is scheduled. if not -- at least he has been warned before and had quiet some time before the emergency case happens. right now the desaster will happen without any notification... - never do any admin work (esp. updates) without proper/decent/checked backup [tm] ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.