Are you talking about the arch or ~arch busybox here? I assume just
arch.

I've done a fair amount of work recently on the _preX stuff in portage
and pretty much have enabled every feature known to build. If it's not
enabled then it means I could not get it to build. But a few of it's
options are controlled already via USE flags.

I'd personally rather not even bother with the arch busybox if you/we
can help it. There just has been so many bugs worked out in the _preX
series and they are using _pre5 for the livecd's that are about to be
released within gentoo but with an added crypto patch
http://dev.gentoo.org/~lu_zero/busybox/crypto-losetup.patch

On Tue, 2004-01-20 at 18:35, david@... wrote:
> I noticed that the default busybox Config.h(the file that selects what applets
> to compile) doesn't include a few things most systems will prolly
> need(freeramdisk for example).
> 
> is there an easy way we can provide people with the capability to
> construct their own customized Config.h and have emerge build busybox
> with that file ?  USE flags are a bit unrealistic in this case.
> like... 'place your own/modify the config in
> .../busybox/files/Config.h'
> 
> I'm sure the people who have done gentoo development type things for
> longer than I have can think of a better place to do this.
> 
> --
> gentoo-embedded@g.o mailing list
-- 
Ned Ludd <solar@g.o>
Gentoo Linux Developer