1 |
Are you talking about the arch or ~arch busybox here? I assume just |
2 |
arch. |
3 |
|
4 |
I've done a fair amount of work recently on the _preX stuff in portage |
5 |
and pretty much have enabled every feature known to build. If it's not |
6 |
enabled then it means I could not get it to build. But a few of it's |
7 |
options are controlled already via USE flags. |
8 |
|
9 |
I'd personally rather not even bother with the arch busybox if you/we |
10 |
can help it. There just has been so many bugs worked out in the _preX |
11 |
series and they are using _pre5 for the livecd's that are about to be |
12 |
released within gentoo but with an added crypto patch |
13 |
http://dev.gentoo.org/~lu_zero/busybox/crypto-losetup.patch |
14 |
|
15 |
On Tue, 2004-01-20 at 18:35, david@×××××××××.com wrote: |
16 |
> I noticed that the default busybox Config.h(the file that selects what applets |
17 |
> to compile) doesn't include a few things most systems will prolly |
18 |
> need(freeramdisk for example). |
19 |
> |
20 |
> is there an easy way we can provide people with the capability to |
21 |
> construct their own customized Config.h and have emerge build busybox |
22 |
> with that file ? USE flags are a bit unrealistic in this case. |
23 |
> like... 'place your own/modify the config in |
24 |
> .../busybox/files/Config.h' |
25 |
> |
26 |
> I'm sure the people who have done gentoo development type things for |
27 |
> longer than I have can think of a better place to do this. |
28 |
> |
29 |
> -- |
30 |
> gentoo-embedded@g.o mailing list |
31 |
-- |
32 |
Ned Ludd <solar@g.o> |
33 |
Gentoo Linux Developer |