[PATCH] image.bbclass: IMAGE_VARS->IMAGE_BOOT, make overridable

[PATCH] image.bbclass: IMAGE_VARS->IMAGE_BOOT, make overridable

[Roman I Khimov]

IMAGE_VARS usage forces images to have init, dev management, login
management and other stuff. In cases where you don't need any of those
(like initramfs images or other special-purpose images) you need to
override 4 variables in order to get clean image that only installs
things from IMAGE_INSTALL.

So, this changes IMAGE_VARS to more meaningful IMAGE_BOOT and makes it
possible to build images without boot components with single
IMAGE_BOOT="".
---
 classes/image.bbclass |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/classes/image.bbclass b/classes/image.bbclass
index fd0df4d..9012de2 100644
--- a/classes/image.bbclass
+++ b/classes/image.bbclass
@@ -17,16 +17,16 @@ IMAGE_INITSCRIPTS ?= "initscripts"
 #
 IMAGE_LOGIN_MANAGER ?= "tinylogin"
 
-IMAGE_VARS = "${IMAGE_INITSCRIPTS} \
+IMAGE_BOOT ?= "${IMAGE_INITSCRIPTS} \
 ${IMAGE_DEV_MANAGER} \
 ${IMAGE_INIT_MANAGER} \
 ${IMAGE_LOGIN_MANAGER} "
 
-RDEPENDS += "${IMAGE_INSTALL} ${IMAGE_VARS}"
+RDEPENDS += "${IMAGE_INSTALL} ${IMAGE_BOOT}"
 
 # "export IMAGE_BASENAME" not supported at this time
 IMAGE_BASENAME[export] = "1"
-export PACKAGE_INSTALL ?= "${IMAGE_INSTALL} ${IMAGE_VARS}"
+export PACKAGE_INSTALL ?= "${IMAGE_INSTALL} ${IMAGE_BOOT}"
 
 # We need to recursively follow RDEPENDS and RRECOMMENDS for images
 do_rootfs[recrdeptask] += "do_deploy do_populate_staging"
-- 
1.6.2.1


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

Re: [PATCH] image.bbclass: IMAGE_VARS->IMAGE_BOOT, make overridable

[Otavio Salvador]

Acked-by: Otavio Salvador <otavio@ossystems.com.br>

On Thu, Apr 16, 2009 at 8:47 AM, Roman I Khimov <khimov@altell.ru> wrote:
> IMAGE_VARS usage forces images to have init, dev management, login
> management and other stuff. In cases where you don't need any of those
> (like initramfs images or other special-purpose images) you need to
> override 4 variables in order to get clean image that only installs
> things from IMAGE_INSTALL.
>
> So, this changes IMAGE_VARS to more meaningful IMAGE_BOOT and makes it
> possible to build images without boot components with single
> IMAGE_BOOT="".
> ---
>  classes/image.bbclass |    6 +++---
>  1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/classes/image.bbclass b/classes/image.bbclass
> index fd0df4d..9012de2 100644
> --- a/classes/image.bbclass
> +++ b/classes/image.bbclass
> @@ -17,16 +17,16 @@ IMAGE_INITSCRIPTS ?= "initscripts"
>  #
>  IMAGE_LOGIN_MANAGER ?= "tinylogin"
>
> -IMAGE_VARS = "${IMAGE_INITSCRIPTS} \
> +IMAGE_BOOT ?= "${IMAGE_INITSCRIPTS} \
>  ${IMAGE_DEV_MANAGER} \
>  ${IMAGE_INIT_MANAGER} \
>  ${IMAGE_LOGIN_MANAGER} "
>
> -RDEPENDS += "${IMAGE_INSTALL} ${IMAGE_VARS}"
> +RDEPENDS += "${IMAGE_INSTALL} ${IMAGE_BOOT}"
>
>  # "export IMAGE_BASENAME" not supported at this time
>  IMAGE_BASENAME[export] = "1"
> -export PACKAGE_INSTALL ?= "${IMAGE_INSTALL} ${IMAGE_VARS}"
> +export PACKAGE_INSTALL ?= "${IMAGE_INSTALL} ${IMAGE_BOOT}"
>
>  # We need to recursively follow RDEPENDS and RRECOMMENDS for images
>  do_rootfs[recrdeptask] += "do_deploy do_populate_staging"
> --
> 1.6.2.1
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>



-- 
Otavio Salvador                  O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854         http://projetos.ossystems.com.br

Re: [PATCH] image.bbclass: IMAGE_VARS->IMAGE_BOOT, make overridable

[Roman I Khimov]

On Thursday 16 April 2009 15:47:01 Roman I Khimov wrote:
>  classes/image.bbclass |    6 +++---

ping

Re: [PATCH] image.bbclass: IMAGE_VARS->IMAGE_BOOT, make overridable

[Koen Kooi]

I think this should be done in a slightly different way, but that can be 
done after this is in.

Acked-by: Koen Kooi <koen@openembedded.org>


On 16-04-09 13:47, Roman I Khimov wrote:
> IMAGE_VARS usage forces images to have init, dev management, login
> management and other stuff. In cases where you don't need any of those
> (like initramfs images or other special-purpose images) you need to
> override 4 variables in order to get clean image that only installs
> things from IMAGE_INSTALL.
>
> So, this changes IMAGE_VARS to more meaningful IMAGE_BOOT and makes it
> possible to build images without boot components with single
> IMAGE_BOOT="".
> ---
>   classes/image.bbclass |    6 +++---
>   1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/classes/image.bbclass b/classes/image.bbclass
> index fd0df4d..9012de2 100644
> --- a/classes/image.bbclass
> +++ b/classes/image.bbclass
> @@ -17,16 +17,16 @@ IMAGE_INITSCRIPTS ?= "initscripts"
>   #
>   IMAGE_LOGIN_MANAGER ?= "tinylogin"
>
> -IMAGE_VARS = "${IMAGE_INITSCRIPTS} \
> +IMAGE_BOOT ?= "${IMAGE_INITSCRIPTS} \
>   ${IMAGE_DEV_MANAGER} \
>   ${IMAGE_INIT_MANAGER} \
>   ${IMAGE_LOGIN_MANAGER} "
>
> -RDEPENDS += "${IMAGE_INSTALL} ${IMAGE_VARS}"
> +RDEPENDS += "${IMAGE_INSTALL} ${IMAGE_BOOT}"
>
>   # "export IMAGE_BASENAME" not supported at this time
>   IMAGE_BASENAME[export] = "1"
> -export PACKAGE_INSTALL ?= "${IMAGE_INSTALL} ${IMAGE_VARS}"
> +export PACKAGE_INSTALL ?= "${IMAGE_INSTALL} ${IMAGE_BOOT}"
>
>   # We need to recursively follow RDEPENDS and RRECOMMENDS for images
>   do_rootfs[recrdeptask] += "do_deploy do_populate_staging"