On Tuesday 31 May 2005 19:55, Wouter Verhelst wrote: > > This would be rather arbitrary and probably be liable to cause > > disagreements. > > Not much more so than with the priorities for the alternatives system. > > I find this quite an interesting idea, really.
Alternatives are down a fairly narrow axis - is text editor X more appropriate to install by default than editor Y which can be argued quite sensibly along the lines of popularity or ease of use for the novice. Is KMail easier to use than the Gimp? Does that question even make sense to ask? > > command line only tools > > enterprise tools (e.g. groupware, RDBMS) > > scientific tools (e.g. octave, R) > > sysadmin tools (e.g. mrtg) > > That could work too; however, in that case the "proviciency level" of > your filter would need to be pretty expert-ish, I'm afraid. Which would > defeat the purpose, kinda. I'm not sure I understand your meaning, could you expand on that a little? I was suggesting that an install that is tagged "novice" or similar would not by default show packages with those tags in listings and searches, installing them only as dependencies. The only user intervention required would be to enable some kind of "expert mode" to get at the hidden packages. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
