![]() |
2010-02-18
, 11:26
|
Posts: 99 |
Thanked: 75 times |
Joined on Nov 2009
|
#12
|
cool...
Now:
There will be no standard procedure for this?
I think it would be useful regardless of whether or not there are problems
with the upgrade. (I think it says to "clean upgrade "...)
![]() |
2010-02-18
, 11:28
|
|
Posts: 3,159 |
Thanked: 2,023 times |
Joined on Feb 2008
@ Finland
|
#13
|
You know it's technically impossible to ensure that the upgrade would work flawlessly with every possible user mod and devel application?
Yeah, the application manager UI could handle conflict situations better (at least give more informative error messages) but they still can be resolved without reflashing with some basic Linux knowledge.
![]() |
2010-02-18
, 11:33
|
Posts: 42 |
Thanked: 8 times |
Joined on Dec 2009
|
#14
|
Yeah, the application manager UI could handle conflict situations better (at least give more informative error messages) but they still can be resolved without reflashing with some basic Linux knowledge.
If you mod/hack/install devel stuff you have three options:
1) Learn how the system works and become knowledgeable enough to solve your problems
2) Ignore the warnings, then reflash and/or whine on the forums when the system stops working
3) Stop messing with stuff you don't understand
I'd suggest either 1 or 3