On Friday 19 January 2007 07:53, Robert Schiele wrote:
On Thu, Jan 18, 2007 at 04:56:43PM +0100, Klaus Kaempf wrote:
* Gerd Hoffmann <kraxel@suse.de> [Jan 18. 2007 16:03]:
chroot: very much depends on what you plan to do with it. The chroots which are created for running daemons in there (named, dhcpd, ...) are smaller than any package on the distro ;) For building packages you don't need network, but some other tools such as make and a compiler.
Exactly. But even for these environments, you probably need a minimal set of packages like glibc, bash, etc. The question is, shouldn't this minimal set be the 'very minimal base' (:-)) pattern ?
This is exactly the reason why you will never reach consensus about _the_ "minimal package set" in my opinion. Actually the _real_ "minimal package set" is having no package at all because having no package at all resolves all dependencies of the packages and there is no package left someone might claim to be unneeded. And this is the _only_ real "minimal package set" that is minimal from a mathematical point of view.
So what people actually mean when they say "minimal package set" is actually either a "what-_I_-want-at-least-on-my-system package set" or a "what-is-needed-for-a-specific-job pattern set". In the first case you will never reach consesus by obvious reasons. In the second case you don't need _the_ "minimal package set" but you need _a_ "minimal package set" for a specific job.
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. With opensuse 10.2 it is very messy trying to configure a system for a specific need. For instance why when removing firefox does Yast want to remove the whole X11 set of packages. I have came across a large number of these dependancy problems when setting up different systems and this can take a large amount of time to resolve. There is also major problems using Yast to set up a software set for autoinstallation. Yast takes the package set of the server it is installed on including all the extra repositories installed on that system e.g packman It is nearly impossible to determine what packages belong to the opensuse ISO package set and all the external packages. -- Regards, Graham Smith --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org