LWN.net Logo

MeeGo: open development and upstream involvement

MeeGo: open development and upstream involvement

Posted Apr 23, 2010 1:47 UTC (Fri) by foom (subscriber, #14868)
In reply to: MeeGo: open development and upstream involvement by bronson
Parent article: MeeGo: open development and upstream involvement

Perhaps your debian days were before debconf was made ubiquitous in Sarge in 2005? For the last few releases, it asks all the questions all up front. (*) And...Debian and Ubuntu use the same system...

(*): ...except for asking what to do about replacing files in you've modified that the package maintainer has also modified...it still asks those one-by-one in the middle of the install. I agree this is a pain in the ass. But you can also disable that, and do like Fedora does and tell it to always replace your configuration files (keeping a backup).

Furthermore, dropping the priority is *not* a terrible idea that never works: all it does is choose the default options.


(Log in to post comments)

MeeGo: open development and upstream involvement

Posted Apr 23, 2010 4:21 UTC (Fri) by rahulsundaram (subscriber, #21946) [Link]

In Fedora, the conf files are not always replaced. It's a bit more complex than that. Refer to

http://www-uxsup.csx.cam.ac.uk/~jw35/docs/rpm_config.html

MeeGo: open development and upstream involvement

Posted Apr 23, 2010 18:33 UTC (Fri) by bronson (subscriber, #4806) [Link]

Yeah, it was probably around then. The problem was that some packagers chose defaults that no sane person would use. Nobody except me complained because nobody except me actually changed the priority.

IIUC, Ubuntu made an effort to cut the number of questions asked by their core packages to zero because it's more user friendly. Not sure if this was actually tracked anywhere but it did seem like Hoary asked fewer stupid questions than Woody.

Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds