Re: [rock-user] How can I create a minimalistic distro? [was:] "Aborted building package glibc23." while building a rock-router distro

Am Samstag, 29. Juli 2006 19:31 schrieb Bernd Schwendele:
> Well, I want to have a minimalistic Distro with x.org for further
> experiments. So the router-config seemed to be the right way. I can't find
> any good docs, describing the targets. The wiki seems to be out of date
> (descr. version 2), no docs in the ROCK/target tree and the help in the
> Config is quite silent and also out of date ;). It's really not that worse,
> but I'm feeling very helpless, although I'm not a linux-newbe. :)
>
> Example:
> ROCKCFG_TARGET:
> - Diet LibC based ROCK Linux:
> 	A distribution using Diet LibC instead of GLibC. DietLibC is
> 	a light-weight C-Library useful for embedded systems and other
> 	low-memory devices.
>
> I can't find "Diet LibC..." entry in the menu. First thought: Do I have
> another Version? 2nd: Is this the right application? ;)

Indeed, the dietlibc target was removed some time ago (but you can still build 
packages against dietlibc). Most other parts of the wiki should still apply, 
though.

>
> (At all, this should be no criticism, please don't misunderstand!)
>
> Furthermore I thought, if I am choosing generic, all packages would be
> installed (& compiled) (help says: A generic, all-purpose distribution that
> has simply everything.) and all I want is a kernel, the basics (hopefully
> without perl) and a x-server.
>
> So what I'm going to do now (btw: thanks for help :) )?
> Choosing generic as target.				OK
> Show expert-only and experimental options.	OK, although I'm not an
> rocklinux expert ;)
>
> - Additional Package Selection:
> "Minimalistic package selection + X.org" chosen!

>
> Do I have to activate the "Custom package selection" and what's about the
> current package list? It shows me kde & all that stuff, I won't have. If I
> am activating "Custom package selection" no change will be shown in the
> current package list in Config-application.

For each configuration you create, packages can be enabled (marked with an X 
in the package list), disabled (marked with O), or completely removed from 
the package list.
Only enabled (aka active) packages are actually build. There are three major 
ways the package list is modified: per target, by package preselection 
templates (the Additional Package Selection given above), and by the custom 
package selection, in that order.
You can use the custom package selection without the additional package 
selection, and vice versa.
Typically you choose a set of active packages with the Additional Package 
Selection that comes closest to what you'd like to have, then maybe 
add/remove additional packages with the custom package selection, if 
necessary.
Btw. these things may be a bit clearer if "Additional Package Selection" is 
renamed to "Package Selection Sets" and "Custom package selection" 
to "Package Selection Rules". Also simply activating the custom package 
selection does nothing if the list of rules is empty.

Hope that helps,
	Stefan Fiedler

>
> Sorry for possibly annoying, but Config-help is confusing me a bit. :s
> Best regards
>   Bernd

-- 
Liberty means responsibility. That is why most men dread it.
  George Bernard Shaw