My Ubuntu installation notes long! 3187

Oliver Wong

Some times there are going to be situations where there is an buttumption of knowledge. I think this is a reasonable one--if you don't know how parbreastioning works, you should just let the installer handle it.

This is why users shouldn't install random packages. It's the mist engine for GTK2. If you don't know what that means, you should either found out or ignore the package.

I don't think that provides any real advantage--I know that I'd rather keep to the existing method. It works very well, and it isn't very confusing. The proposed method sounds like a good way to introduce conflicts and frustrate users.

Use one of the automated package building scripts. Rogue packages are a bad idea on a Debian system, but it's not hard to build a package. It still won't resolve all the dependency issues, but at least it's easy to remove-upgrade when needed.

And I don't think it's realistic to try to fit two different paradigms into the same UI. How would I know if I'm supposed to appease the Unix users, the Windows users, or the Mac users? I can't very well blend the three, since each make different buttumptions about what the user should do.

This is, however, going to be nearly impossible to practically implement, given the manner in which GNU-Linux applications tend to be developed.

What else would it do? Nothing, I suppose.