فهرست منبع

system: change label for BR2_INIT_NONE

Currently, the label reads "None", but it can be a bit misleading.
Indeed, since its inception in 0c00636e8bbc (system/init: add option for
no init system), what it really meant was "none of the above", as
briefly laid out in the commit log for 0c00636e8bbc (typo included):

    Can be usefull if a local package provides an init procedure.

This was later refined in 4d185e5ec51b (system: add help entry to "none"
init system), which explained:

    Add a comment that states the user has to provide his own init
    system, either via a package or a rootfs overlay.

So, change the label to better reflect that.

Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Cc: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Reviewed-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Yann E. MORIN 11 ماه پیش
والد
کامیت
436e39913e
1فایلهای تغییر یافته به همراه1 افزوده شده و 1 حذف شده
  1. 1 1
      system/Config.in

+ 1 - 1
system/Config.in

@@ -146,7 +146,7 @@ comment "systemd highly recommends Linux >= 4.15"
 	depends on !BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_15
 	depends on !BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_15
 
 
 config BR2_INIT_NONE
 config BR2_INIT_NONE
-	bool "None"
+	bool "Custom (none)"
 	select BR2_PACKAGE_SKELETON_INIT_NONE if BR2_ROOTFS_SKELETON_DEFAULT
 	select BR2_PACKAGE_SKELETON_INIT_NONE if BR2_ROOTFS_SKELETON_DEFAULT
 	help
 	help
 	  Buildroot will not install any init system. You will
 	  Buildroot will not install any init system. You will