public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Silvano Cirujano Cuesta <silvano.cirujano-cuesta@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH] fix: remove unneeded unconditional recipes
Date: Wed, 14 Apr 2021 09:45:39 +0200	[thread overview]
Message-ID: <c3829e5c-03a3-0bf4-8e07-f80b8c03bfe0@siemens.com> (raw)
In-Reply-To: <da90d78d-a3ba-8989-5222-7dafebf6c839@siemens.com>



On 13/04/2021 18:01, Jan Kiszka wrote:
> On 13.04.21 17:26, [ext] Silvano Cirujano Cuesta wrote:
>> Commit 9c3499adf91 introduced the unconditional inclusion of the recipes
>> isar-exclude-docs and isar-disable-apt-cache, but they are only needed
>> for container images.
>>
> 
> In fact, are those packages truly needed or just desirable, reasonable
> defaults?

I was yesterday about to write "reasonable defaults"...
But after having faced some difficulties to find a robust implementation to keep it, I decided to reconsider it.

After having slept over it, I think IT'S NOT EVEN A REASONABLE DEFAULT 8-o

It's a storage optimization that is only being used in "slim" images.
Having used debian "slim" images as a size reference brought me to introduce it.

So I'll send a new patch completely removing it.
If we want to later on offer that optimization as an optional feature, we can do so.

  Silvano

> 
> In any case, it might be worth documenting those defaults as well. They
> can be overwritten (IMAGE_INSTALL_remove), but the users should be made
> aware of them.
> 
> Jan
> 
>> Signed-off-by: Silvano Cirujano Cuesta <silvano.cirujano-cuesta@siemens.com>
>> ---
>>  meta/classes/container-img.bbclass             | 2 ++
>>  meta/classes/image-container-extension.bbclass | 1 -
>>  2 files changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/meta/classes/container-img.bbclass b/meta/classes/container-img.bbclass
>> index 79ef3e8..887d49e 100644
>> --- a/meta/classes/container-img.bbclass
>> +++ b/meta/classes/container-img.bbclass
>> @@ -6,6 +6,8 @@
>>  # This class provides the task 'containerize_rootfs'
>>  # to create container images containing the target rootfs.
>>  
>> +IMAGE_INSTALL += "isar-exclude-docs isar-disable-apt-cache"
>> +
>>  do_container_image[stamp-extra-info] = "${DISTRO}-${MACHINE}"
>>  do_container_image[vardeps] += "CONTAINER_FORMATS"
>>  do_container_image(){
>> diff --git a/meta/classes/image-container-extension.bbclass b/meta/classes/image-container-extension.bbclass
>> index f693627..e26604a 100644
>> --- a/meta/classes/image-container-extension.bbclass
>> +++ b/meta/classes/image-container-extension.bbclass
>> @@ -6,7 +6,6 @@
>>  # This class extends the image.bbclass for containerizing the root filesystem.
>>  
>>  CONTAINER_FORMATS ?= "docker-archive"
>> -IMAGE_INSTALL += "isar-exclude-docs isar-disable-apt-cache"
>>  
>>  containerize_rootfs() {
>>      local cmd="/bin/dash"
>>
> 
-- 
  Silvano Cirujano Cuesta
-- 
Siemens AG, T RDA IOT SES-DE
Corporate Competence Center Embedded Linux


      reply	other threads:[~2021-04-14  7:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-13 15:26 Silvano Cirujano Cuesta
2021-04-13 16:01 ` Jan Kiszka
2021-04-14  7:45   ` Silvano Cirujano Cuesta [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c3829e5c-03a3-0bf4-8e07-f80b8c03bfe0@siemens.com \
    --to=silvano.cirujano-cuesta@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox