[gentoo-embedded] Re: portage profiles for alternatives (uclibc)

[Mike Frysinger]

On Thursday 10 June 2004 05:07 am, Peter S. Mazinger wrote:
> All the profiles use direct names for the packages[.build] or in the
> base|embedded|hardened new stackable structure (is stackable working?)
> like app-arch/tar (the ebuilds refer also to this). For embedded/uclibc,
> this could be replaced by busybox, or yacc could be replaced by using
> bison's yacc.bison shell script.

stackable is *supposed* to be working i believe with latest 2.0.51

> The current approach does not allow replacement of some/all of the
> packages for other platforms, my proposal would be to use only virtual
> names for build/system and define these differently for glibc/uclibc (and
> maybe others).

simple answer, no
that's the point of the stackable profiles ... you can add/delete packages 
from parent profiles in your sub-profile

the changes you list are just not worth the gained cruft in the standard  
profiles ... in your embeded profile, setup a virtual file where busybox 
provides all the stuff you want it to

> 1. the gettext package is always required for emerge system (but this in
> most cases only an nls requirement), building w/o nls does not/should not
> need gettext (some packages need patches for this)

yes but when patching configure.in and related files and re-running 
`autoconf`, the process will fail if the file refers to NLS stuff and 
gettext, not being installed on the system, did not provide all the m4 and 
related files

> 2. groff requires c++ (and is used by man), if an embedded system does not
> 3. uclibc does not support pam, so the package pam/pam-login/pwdb should
> snip

see above about adding/deleting packages from the profile
-mike

--
gentoo-embedded@g.o mailing list