From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: "Moessbauer,
Felix (FT RPD CED OES-DE)" <felix.moessbauer@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH] expand-on-first-boot: Add missing dependency for btrfs
Date: Mon, 11 Nov 2024 09:32:36 +0100 [thread overview]
Message-ID: <5b0057cf-c01f-482f-9b91-fbe12119b202@siemens.com> (raw)
In-Reply-To: <8939bc189690f9024f766c999e36edcc8df05294.camel@siemens.com>
On 11.11.24 09:24, Moessbauer, Felix (FT RPD CED OES-DE) wrote:
> On Fri, 2024-11-08 at 12:36 +0100, 'Jan Kiszka' via isar-users wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> This was forgotten in 412059fc8f5f.
>>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>>
>> Needs to go on top of
>> https://patchwork.isar-build.org/project/isar/patch/5b0f1ad9-3d12-4d05-a5e4-bb9dcf258545@siemens.com/
>>
>> ...-first-boot_1.5.bb => expand-on-first-boot_1.6.bb} | 11
>> ++++++++++-
>> 1 file changed, 10 insertions(+), 1 deletion(-)
>> rename meta/recipes-support/expand-on-first-boot/{expand-on-first-
>> boot_1.5.bb => expand-on-first-boot_1.6.bb} (75%)
>>
>> diff --git a/meta/recipes-support/expand-on-first-boot/expand-on-
>> first-boot_1.5.bb b/meta/recipes-support/expand-on-first-boot/expand-
>> on-first-boot_1.6.bb
>> similarity index 75%
>> rename from meta/recipes-support/expand-on-first-boot/expand-on-
>> first-boot_1.5.bb
>> rename to meta/recipes-support/expand-on-first-boot/expand-on-first-
>> boot_1.6.bb
>> index 4b9cf376..071bed24 100644
>> --- a/meta/recipes-support/expand-on-first-boot/expand-on-first-
>> boot_1.5.bb
>> +++ b/meta/recipes-support/expand-on-first-boot/expand-on-first-
>> boot_1.6.bb
>> @@ -10,7 +10,16 @@ inherit dpkg-raw
>> DESCRIPTION = "This service grows the last partition to the full
>> medium during first boot"
>> MAINTAINER = "isar-users <isar-users@googlegroups.com>"
>>
>> -DEBIAN_DEPENDS = "systemd, sed, grep, coreutils, mount, e2fsprogs,
>> fdisk (>=2.29.2-3) | util-linux (<2.29.2-3), util-linux"
>> +DEBIAN_DEPENDS = " \
>> + systemd, \
>> + sed, \
>> + grep, \
>> + coreutils, \
>> + mount, \
>> + btrfs-progs, \
>
> By that we unconditionally pull in the btrfs-progs, despite most images
> not using btrfs. Why not just emit a meaningful error message in case
> we try to resize a btrfs. Then people can add the tool to the image
> directly.
We also pull e2fsprogs even when not using it. If we want to make this
more efficient, we would have to ask the user for opting-out from unused
formats.
Given the current state of the script, this here is correct, the other
thing is an optimization.
Jan
--
Siemens AG, Technology
Linux Expert Center
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/5b0057cf-c01f-482f-9b91-fbe12119b202%40siemens.com.
next prev parent reply other threads:[~2024-11-11 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 11:36 'Jan Kiszka' via isar-users
2024-11-11 8:24 ` 'MOESSBAUER, Felix' via isar-users
2024-11-11 8:32 ` 'Jan Kiszka' via isar-users [this message]
2024-11-18 6:11 ` Uladzimir Bely
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=5b0057cf-c01f-482f-9b91-fbe12119b202@siemens.com \
--to=isar-users@googlegroups.com \
--cc=felix.moessbauer@siemens.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