Am Mittwoch 27 Februar 2008 schrieb Lukas Ocilka:
Maybe we should start with questions: * Why could user want to remove a pattern at all?
* How are patterns currently designed? What they contain? They are grouping functionality by toplevel dependencies. It's more likely
Because they want to save room and don't care for "Games". Or they tried "KDE" and figured it has nothing to do with the Kentucky Deparetment of Education. that a package is only in pattern, even though it's far from a rule.
* Are there packages that are not in any pattern but installed automatically by solver (libraries, for instance)? (similar to the previous question). Roughly 15% packages of a full install are not listed in any pattern. Language dependencies, hardware specifics or libraries.
We should imagine the situation when user wants to remove something (pattern, language) and imagine what makes him do it. Then we can understand and design the workflow better.
Well, if Joe deletes "Office" functionality, he no longer cares for attachments sent by his mother, so he doesn't want to have no ooimpress blocking him from saving ripped CDs :) Greetings, Stephan -- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org