Re: [OE-core] [PATCH 0/4] add variable INSTALL_ALL to install all packages in recipes
On 01/08/2015 07:55 PM, Otavio Salvador wrote: On Thu, Jan 8, 2015 at 12:27 AM, Hongxu Jia hongxu@windriver.com wrote: On 01/08/2015 07:54 AM, Richard Purdie wrote: This tells me what the change does. What it doesn't say is why we need this? Its a fairly invasive set of changes but I don't see the usecase... Hi Richard, I am sorry not to say it clearly, 1) We have been asked many times on how to install all the PACKAGES of a recipe, we can only list them one by one in the RDPENDS (or IMAGE_INSTALL and so on) currently, especially like dynamic generated packages (perl-modules, kernel-modules) which depends on many other packages, it is not easy to remember these package names for customer. It is helpful for user who does not take care the details that how many packages generated in a recipe, just want to directly install all of them. 2) Providing a mechanism to install all the PACKAGES of a recipe is helpful to test all generated packages of a recipe could work, such as the defect of '[PATCH 3/4]' was found by installing all packages of python3. 3) The fix is based on the usage of IMAGE_INSTALL, so it doesn't affect the users who do not want to use this feature (We disable it by default). For me, it seems those should have a meta package, not a new install variable fo this. What meta package means? I am sorry I don't quite follow it. //Hongxu -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 0/4] add variable INSTALL_ALL to install all packages in recipes
On Thu, Jan 8, 2015 at 10:06 AM, Hongxu Jia hongxu@windriver.com wrote: On 01/08/2015 07:55 PM, Otavio Salvador wrote: On Thu, Jan 8, 2015 at 12:27 AM, Hongxu Jia hongxu@windriver.com wrote: On 01/08/2015 07:54 AM, Richard Purdie wrote: This tells me what the change does. What it doesn't say is why we need this? Its a fairly invasive set of changes but I don't see the usecase... Hi Richard, I am sorry not to say it clearly, 1) We have been asked many times on how to install all the PACKAGES of a recipe, we can only list them one by one in the RDPENDS (or IMAGE_INSTALL and so on) currently, especially like dynamic generated packages (perl-modules, kernel-modules) which depends on many other packages, it is not easy to remember these package names for customer. It is helpful for user who does not take care the details that how many packages generated in a recipe, just want to directly install all of them. 2) Providing a mechanism to install all the PACKAGES of a recipe is helpful to test all generated packages of a recipe could work, such as the defect of '[PATCH 3/4]' was found by installing all packages of python3. 3) The fix is based on the usage of IMAGE_INSTALL, so it doesn't affect the users who do not want to use this feature (We disable it by default). For me, it seems those should have a meta package, not a new install variable fo this. What meta package means? I am sorry I don't quite follow it. Like we do for gstreamer; gstreamer1.0-plugins-good-meta, for example. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 0/4] add variable INSTALL_ALL to install all packages in recipes
On Thu, Jan 8, 2015 at 12:27 AM, Hongxu Jia hongxu@windriver.com wrote: On 01/08/2015 07:54 AM, Richard Purdie wrote: This tells me what the change does. What it doesn't say is why we need this? Its a fairly invasive set of changes but I don't see the usecase... Hi Richard, I am sorry not to say it clearly, 1) We have been asked many times on how to install all the PACKAGES of a recipe, we can only list them one by one in the RDPENDS (or IMAGE_INSTALL and so on) currently, especially like dynamic generated packages (perl-modules, kernel-modules) which depends on many other packages, it is not easy to remember these package names for customer. It is helpful for user who does not take care the details that how many packages generated in a recipe, just want to directly install all of them. 2) Providing a mechanism to install all the PACKAGES of a recipe is helpful to test all generated packages of a recipe could work, such as the defect of '[PATCH 3/4]' was found by installing all packages of python3. 3) The fix is based on the usage of IMAGE_INSTALL, so it doesn't affect the users who do not want to use this feature (We disable it by default). For me, it seems those should have a meta package, not a new install variable fo this. -- Otavio Salvador O.S. Systems http://www.ossystems.com.brhttp://code.ossystems.com.br Mobile: +55 (53) 9981-7854Mobile: +1 (347) 903-9750 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 0/4] add variable INSTALL_ALL to install all packages in recipes
This tells me what the change does. What it doesn't say is why we need this? Its a fairly invasive set of changes but I don't see the usecase... Cheers, Richard -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH 0/4] add variable INSTALL_ALL to install all packages in recipes
On 01/08/2015 07:54 AM, Richard Purdie wrote: This tells me what the change does. What it doesn't say is why we need this? Its a fairly invasive set of changes but I don't see the usecase... Hi Richard, I am sorry not to say it clearly, 1) We have been asked many times on how to install all the PACKAGES of a recipe, we can only list them one by one in the RDPENDS (or IMAGE_INSTALL and so on) currently, especially like dynamic generated packages (perl-modules, kernel-modules) which depends on many other packages, it is not easy to remember these package names for customer. It is helpful for user who does not take care the details that how many packages generated in a recipe, just want to directly install all of them. 2) Providing a mechanism to install all the PACKAGES of a recipe is helpful to test all generated packages of a recipe could work, such as the defect of '[PATCH 3/4]' was found by installing all packages of python3. 3) The fix is based on the usage of IMAGE_INSTALL, so it doesn't affect the users who do not want to use this feature (We disable it by default). //Hongxu Cheers, Richard -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
[OE-core] [PATCH 0/4] add variable INSTALL_ALL to install all packages in recipes
Test Steps: Install busybox and lib32-python3 to core-image-minimal, and also install all available packages of recipes busybox and python3. 1. vim local.conf ... MACHINE ?= qemux86-64 require conf/multilib.conf MULTILIBS = multilib:lib32 DEFAULTTUNE_virtclass-multilib-lib32 = x86 IMAGE_INSTALL_append = busybox lib32-python3 INSTALL_ALL_busybox ?= 1 INSTALL_ALL_lib32-python3 ?= 1 ... 2. Build core-image-minimal $ bitbake core-image-minimal 3. Check installed_pkgs.txt, all available packages of recipes busybox and lib32-python3 have been installed. ... $ cat tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/installed_pkgs.txt ... busybox core2-64 busybox-hwclock core2-64 busybox-syslog core2-64 busybox-udhcpc core2-64 busybox-udhcpd core2-64 ... 4. Edit local.conf to assign INSTALL_ALL_busybox ?= 0 5. build core-image-minimal 6. Check installed_pkgs.txt, busybox-udhcpd not installed ... $ cat tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/installed_pkgs.txt ... busybox core2-64 busybox-hwclock core2-64 busybox-syslog core2-64 busybox-udhcpc core2-64 ... //Hongxu The following changes since commit bfe7d3032a61a20010b5b758be07581e1bf01cba: gstreamer1.0-omx: use mulitple SCMs to fetch submodules (2014-12-31 17:04:52 +) are available in the git repository at: git://git.pokylinux.org/poky-contrib hongxu/install-all http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=hongxu/install-all Hongxu Jia (4): scripts/oe-pkgdata-util: support rprovides for lookup-recipe scripts/oe-pkgdata-util: add ability to list all produced packages from a recipe python3: avoid debian renaming for libpython3 manifest.py/image.bbclass: add var-INSTALL_ALL to install all packages of a recipes. meta/classes/image.bbclass| 19 - meta/lib/oe/manifest.py | 56 +- meta/recipes-devtools/python/python3_3.3.3.bb | 2 + scripts/oe-pkgdata-util | 101 +- 4 files changed, 174 insertions(+), 4 deletions(-) -- 1.9.1 -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
