From: Henning Schild <henning.schild@siemens.com>
To: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
Cc: isar-users@googlegroups.com, "Schmidl,
Tobias" <tobiasschmidl@siemens.com>
Subject: Re: [PATCH 1/1] expand last partition supports btrfs
Date: Fri, 30 Sep 2022 20:25:08 +0200 [thread overview]
Message-ID: <20220930202508.2247737d@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <CAJGKYO7oJhD41xUQZW=X43yTY3wf1m31MJVz6NSofbW3pR8Hdw@mail.gmail.com>
Am Fri, 30 Sep 2022 19:37:09 +0200
schrieb "Roberto A. Foglietta" <roberto.foglietta@gmail.com>:
> Il giorno ven 30 set 2022 alle ore 13:42 Henning Schild <
> henning.schild@siemens.com> ha scritto:
>
> >
> > Feel free to apply that patch in your layer, you can likely bbappend
> > somehow and do not actually have to patch isar.
> >
>
> Geniale!
That sounds like the trick works for you. Make sure to revert it once
the systemd patches are merged and you switch to a new isar. But i
assume the version will be bumped so the append will tell you that it
does not work any longer.
> However the fact that DEBIAN_DEPENDS requires a comma separation that
> upsets me.
We once tried to make that more OE but that is hard. Here you just have
a string that makes it into the control file. It can contain things
like "or" operators and versions. Too debian-specific to find a good
way to apply OE standards on it.
> $ cat
> recipes-support/expand-on-first-boot/expand-on-first-boot_1.1.bbappend
>
> DEBIAN_DEPENDS += ", btrfs-progs"
>
> FILESEXTRAPATHS_prepend := "${THISDIR}:"
>
> SRC_URI += "file://expand-last-partition.sh"
>
> The second thing that upset me is that ${THISDIR}: search always on
> /debx86 which is the name of the layer
Mhh you layer.conf should have LAYERDIR_debx86 defined. And you can go
FILESEXTRAPATHS_prepend :=
"${LAYERDIR_debx86}/recipes-support/expand-on-first-boot/files:"
regards,
Henning
> /build/../repo/recipes-support/expand-on-first-boot/debx86
>
> In case I use this one ${THISDIR}/files: then the path would be
> debx86/files - mumble mumble
>
> Thanks, R.
next prev parent reply other threads:[~2022-09-30 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM0PR10MB2020D00D6BBFAA81427A64A6AA569@AM0PR10MB2020.EURPRD10.PROD.OUTLOOK.COM>
2022-09-30 7:43 ` Roberto A. Foglietta
2022-09-30 10:58 ` Henning Schild
2022-09-30 11:29 ` Roberto A. Foglietta
2022-09-30 11:42 ` Henning Schild
2022-09-30 17:37 ` Roberto A. Foglietta
2022-09-30 18:25 ` Henning Schild [this message]
2022-10-01 14:35 ` Roberto A. Foglietta
2022-10-04 22:16 ` Roberto A. Foglietta
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=20220930202508.2247737d@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=roberto.foglietta@gmail.com \
--cc=tobiasschmidl@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