Bug 91555 – busybox local config is not relative ${ROOT}

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Natanael Copa 2005-05-05 04:23:26 UTC]

You cannot have different busybox with different local configs in different ${ROOT} since the ebuild looks for the busybox configuration relative hardcoded / and not relative ${ROOT}

This makes problems if you have several different embedded projects in the same environment or need a different busybox for things like initrd.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

[Comment 1 Natanael Copa 2005-05-05 04:25:44 UTC]

Created attachment 58126 [details, diff]
patch for busybox-1.00-r3.ebuild

Added a ${ROOT} where the ebuild looks for the local config.

[Comment 2 SpanKY 2005-05-07 03:08:20 UTC]

it'd be better to have it check $ROOT first and then fall back to /

[Comment 3 Natanael Copa 2005-05-07 04:02:39 UTC]

Created attachment 58266 [details, diff]
busybox-1.00-r3.ebuild.patch

If it does not find any config file in $ROOT/etc/busybox/... it fallbacks to
the system wide /etc/busybox/...

[Comment 4 Natanael Copa 2005-05-07 04:07:37 UTC]

Just a thought... if USE=savedconfig is specified and no config is found, shouldn't emerge fail?

I had a situation where I had a statically linked busybox in initrd but the config was never read. It took me some time to find out that it was busybox in the initrd that was dynamically linked.

[Comment 5 solar (RETIRED) 2005-05-07 06:01:37 UTC]

No I do not want it to fail if no bb.config is found.

[Comment 6 solar (RETIRED) 2005-05-07 06:16:21 UTC]

Patch added to -r3 thanks Natanael