| 1 |
>>>> However if I perform an emerge world: |
| 2 |
>>>> PORTAGE_CONFIGROOT=[...] ROOT=[...] emerge world -vp |
| 3 |
>>>> |
| 4 |
>>>> Portage wants to merge: |
| 5 |
>>>> virtual/editor-0 |
| 6 |
>>>> app-editors/nano |
| 7 |
>>>> |
| 8 |
>>>> virtual/pager-0 |
| 9 |
>>>> sys-apps/less |
| 10 |
>>>> |
| 11 |
>>>> I have enabled less and vi in my busybox, therefore I don't want to |
| 12 |
>>>> install an "external" pager and editor. |
| 13 |
>>> use the profile's package.provided then |
| 14 |
>> Yes, that's what I do at the moment... However it would be much nicer if |
| 15 |
>> the powerful gentoo use and dependency system could be used for this. |
| 16 |
>> |
| 17 |
>> Furthermore BusyBox init-scripts (for crond, syslogd etc.) could be |
| 18 |
>> installed according to the enabled use-flags, rather than manually. |
| 19 |
> |
| 20 |
> With as many features as busybox supports this could get out of control |
| 21 |
> quickly with USE= flags for per-options. |
| 22 |
|
| 23 |
That's true. On the other hand, providing use-flags only for existing |
| 24 |
virtuals (for example cron, syslog, tar, pager, editor etc.), should |
| 25 |
avoid an overblown use-list. In addition ebuilds such as php or apache |
| 26 |
also come with a fair amount of use flags (which is really handy, in my |
| 27 |
opinion). |
| 28 |
|
| 29 |
|
| 30 |
>> Is there something that speaks against such a change? |
| 31 |
>> |
| 32 |
>> If not, I'm willing to provide the necessary patches |
| 33 |
> |
| 34 |
> Patches are always most welcome. But I sorta rather tie it to something |
| 35 |
> more simple. Like maybe when 'make-symlinks' is enabled. One can assume |
| 36 |
> he/she is using busybox for the core system. |
| 37 |
|
| 38 |
Good point, thanks. |
| 39 |
|
| 40 |
|
| 41 |
regards |
| 42 |
Chris |
Archives