On Thu, 2003-11-06 at 19:45, Justin Huff wrote:
> > > We're kicking around the idea of creating profile(s) for the systems,
> > > which would obviously have the bare minimum for operation and would be
> > > using uClibc.
> > >
> > I'd suggest you use glibc at the moment.  A uClibc-based build will be
> > incompatible with all the pre-existing binaries.
> 
> I think it's very worthwhile to support both glibc and uclibc (and maybe
> dietlibc).  Not all embedded systems have very tight space constraints. 
> I'm working on a system here that I'm going to have 64meg of flash for
> the system.  I don't need to get all that tight.

Ok, well I guess I stated this too absolutely.  uClibc is the main libc
target, but this is still Gentoo.  We're not trying to eliminate
people's choice.  But making the profile big by making glibc default is
a disservice to people who really have resource constraints.  So most
likely the best thing would be to set uClibc as the default for
virtual/glibc (fix the uClibc ebuilds if needed) and put virtual/glibc
in the profile.  Then the choice will still remain, if glibc is
wanted/needed.

-- 
Chris PeBenito
<pebenito@g.o>
Developer, SELinux
Hardened Gentoo Linux
Embedded Gentoo Linux
 
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE6AF9243
Key fingerprint = B0E6 877A 883F A57A 8E6A  CB00 BC8E E42D E6AF 9243