On Tue, Jun 13, 2017 at 03:37:00PM +0200, Daniel Schultz wrote:
> This patch adds a further layer to the config hierarchy. It allows a
> dynamic configuration of expansions.
>
> Signed-off-by: Daniel Schultz <d.schultz@xxxxxxxxx>
> ---
> defaultenv/defaultenv-2-base/bin/init | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/defaultenv/defaultenv-2-base/bin/init b/defaultenv/defaultenv-2-base/bin/init
> index 7af3c7d..a93ea58 100644
> --- a/defaultenv/defaultenv-2-base/bin/init
> +++ b/defaultenv/defaultenv-2-base/bin/init
> @@ -25,6 +25,7 @@ magicvar -a global.allow_color "Allow color on the console (boolean)"
> [ -z "${global.editcmd}" ] && global.editcmd=sedit
>
> [ -e /env/config-board ] && /env/config-board
> +[ -e /env/config-expansions ] && /env/config-expansions
I read the last thread again and I think my question remains
unanswered. Why can't you put the config-expansions to /env/init/ and
let it be executed automatically without changing /bin/init?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/barebox
