just to be sure, as i am in no way a programmer:
update-manager performs an 'upgrade' by default. the dependencies and
conflicts of the individual packages currently installed, inform update-
manager if there a additional packages required or packages need to be
removed. if such case happens, then update-manager performes a 'dist-
upgrade' which is based on a backend different from 'upgrade'.
my goal/reason to file this bug report was that either way you do the upgrade,
don't aks the user. hide the complexity. why should a user be bothered if a
package now requires, say python-pygoocanvas?
so why bother adding more
a) interaction
- by informing the user that the upgrade process is different from
default; again, why should the user care?
and
b) confusion
- use a different UI style to do the task.
i hope i'm not sounding disrespectful, cause i really enjoy using
ubuntu. in fact it's the only OS i run. these are just some thoughts
towards a clean and simple UI and a 'linux for human beings'. i see a
danger in dist-upgrade if you're running a development release, cause
there *will* be broken packages/dependencies. but is there great danger
if you're running a stable release?
--
don't ask for a dist-upgrade, just do it
https://bugs.launchpad.net/bugs/136954
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
