| 1 |
On Thu, 2005-07-14 at 12:01 -0400, Michael Cummings wrote: |
| 2 |
> Not sure of the mechanics on how |
| 3 |
> this is done for the portage emerge process, but even stopping the |
| 4 |
> emerge process for those packages that *must* have a preconfig done |
| 5 |
> would help (are there any though? I can think of one maybe, but not |
| 6 |
> really anything to demand new functionality in portage yet). |
| 7 |
|
| 8 |
This problem is mostly present in the embedded world. As the packages |
| 9 |
have to be fine tuned (as a kernel is) at compiled time for the system |
| 10 |
on which it is beiing build. For example, uClibc and busybox uses a |
| 11 |
kernel like config. |
| 12 |
|
| 13 |
As described on busybox's home page: |
| 14 |
|
| 15 |
"BusyBox combines tiny versions of many common UNIX utilities into a |
| 16 |
single small executable. It provides replacements for most of the |
| 17 |
utilities you usually find in GNU fileutils, shellutils, etc. The |
| 18 |
utilities in BusyBox generally have fewer options than their |
| 19 |
full-featured GNU cousins; however, the options that are included |
| 20 |
provide the expected functionality and behave very much like their GNU |
| 21 |
counterparts. BusyBox provides a fairly complete environment for any |
| 22 |
small or embedded system." |
| 23 |
|
| 24 |
With so many applications/options provided by a single package, that aim |
| 25 |
to go in small memory/storage system, one must understand that users |
| 26 |
must fine tune it. |
| 27 |
|
| 28 |
Kristian |
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives