In data sabato 07 dicembre 2013 10:27:09, Stefan Seyfried ha scritto:
Am 07.12.2013 00:22, schrieb Patrick Shanahan:
It is *your* own fault, assume the blame!
While this is certainly one view of the issue, there is another one:
Could we do something in our software to avoid this happening?
Zypper recognizing that it is going to da version update and checking the versions if they are "compatible" for updating, and if not issuing a BIG FAT HONKING WARNING!
I have no idea how this could be implemented, but it is maybe something to think about.
I think that at first we need rpm transaction. This for clean installation and for avoid some issue. Than, what about a script/software called after zypper dup that takes care of special things that need to be done/checked/fixed ? An upgrade package that check OS version and do the needed stuff at least for fixing known issue. This package could be extendend at each release so you could support upgrade from more release. I mean: upgrade from x.x to x.x+1 call upgrade-x.x-x.x+1.sh upgrade from x.x to x.x+2 call upgrade-x.x--x.x-x.x+1.sh and upgrade- x.x--x.x-x.x+2.sh Clearly should be smart enough to do thing only if needed and only one time. Just an idea, I don't known if really doable... Daniele. -- *** Linux user # 198661 ---_ ICQ 33500725 *** *** Home http://www.kailed.net *** *** Powered by openSUSE *** -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org