On Fri, Jan 19, 2007 at 08:55:54AM +1100, Graham Smith wrote:
What might be needed is a "base package set" plus a number of extra pattern sets to cover specific jobs like:-
a) minimal networking b) package management c) virtualised systems
You would then select the "base package set", then whatever patterns you need to configure a certain system. This may need to placed under an advanced section of the package management to reduce the problems faced by newbies.
This is the thinko! Why should one have to select a "base package set" and "minimal networking" if he just wants "minimal networking" (whatever that would be)? Why shouldn't he just select _only_ "minimal networking" if this is what he wants? Sure, your various use cases might have a common kernel but there is no need to make this explicit, the dependency resolver is doing that for you. There is absolutely no point in presenting something without a meaning to the user. Honestly, most people in this thread try to solve a problem that is just not existing. That's like people in "The Hitchhiker's Guide to the Galaxy" trying to find the answer without knowing the question at all. I recommend that people interested in finding a solution for the scenario Andreas was talking about, write this in this thread. People that want to talk about chroot/xen/whatever just first think about what they actually want and if they found that then start a _new_ discussion because posting this in this thread is off-topic and just confusing the discussion. And describe your use case in a _detailed_ way because the less detailed your use case is the more troll-like will be the resulting discussion. Robert -- Robert Schiele Dipl.-Wirtsch.informatiker mailto:rschiele@gmail.com "Quidquid latine dictum sit, altum sonatur."