From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCH 1/2] meta-isar: add example recipe for deploying prebuilt debs
Date: Fri, 12 Feb 2021 19:47:27 +0100 [thread overview]
Message-ID: <20210212194727.743b4732@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <bb2996b2-47a6-d835-0141-5195b09dcbe0@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 3948 bytes --]
Am Fri, 12 Feb 2021 17:42:07 +0100
schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> On 12.02.21 14:17, Henning Schild wrote:
> > From: Henning Schild <henning.schild@siemens.com>
> >
> > Signed-off-by: Henning Schild <henning.schild@siemens.com>
> > ---
> > meta-isar/conf/local.conf.sample | 2 +-
> > .../example-prebuilt-dummy_0.1.bb | 15 ++++++++++++
> > .../example-prebuilt/example-prebuilt_0.1.bb | 23
> > +++++++++++++++++++ 3 files changed, 39 insertions(+), 1 deletion(-)
> > create mode 100644
> > meta-isar/recipes-app/example-prebuilt-dummy/example-prebuilt-dummy_0.1.bb
> > create mode 100644
> > meta-isar/recipes-app/example-prebuilt/example-prebuilt_0.1.bb
> >
> > diff --git a/meta-isar/conf/local.conf.sample
> > b/meta-isar/conf/local.conf.sample index 107496c163..cc0b5c66bb
> > 100644 --- a/meta-isar/conf/local.conf.sample
> > +++ b/meta-isar/conf/local.conf.sample
> > @@ -172,7 +172,7 @@ CONF_VERSION = "1"
> >
> > #
> > # The default list of extra packages to be installed.
> > -IMAGE_INSTALL = "hello-isar example-raw
> > example-module-${KERNEL_NAME} enable-fsck isar-exclude-docs
> > samefile hello isar-disable-apt-cache cowsay" +IMAGE_INSTALL =
> > "hello-isar example-raw example-module-${KERNEL_NAME} enable-fsck
> > isar-exclude-docs samefile hello isar-disable-apt-cache cowsay
> > example-prebuilt" # # Enable cross-compilation support diff --git
> > a/meta-isar/recipes-app/example-prebuilt-dummy/example-prebuilt-dummy_0.1.bb
> > b/meta-isar/recipes-app/example-prebuilt-dummy/example-prebuilt-dummy_0.1.bb
> > new file mode 100644 index 0000000000..92273dc886 --- /dev/null
> > +++
> > b/meta-isar/recipes-app/example-prebuilt-dummy/example-prebuilt-dummy_0.1.bb
> > @@ -0,0 +1,15 @@ +# Sample recipe to create a dummy package used
> > for example-prebuilt +#
> > +# This software is a part of ISAR.
> > +
> > +DESCRIPTION = "Sample application for ISAR"
> > +MAINTAINER = "Your name here <you@domain.com>"
> > +
> > +SRC_URI = ""
> > +
> > +inherit dpkg-raw
> > +
> > +# we provide a deb under another name
> > +do_prepare_build_append() {
> > + sed -i 's/example-prebuilt-dummy/example-prebuilt/g'
> > ${S}/debian/* +}
> > diff --git
> > a/meta-isar/recipes-app/example-prebuilt/example-prebuilt_0.1.bb
> > b/meta-isar/recipes-app/example-prebuilt/example-prebuilt_0.1.bb
> > new file mode 100644 index 0000000000..4f224a48ec --- /dev/null
> > +++ b/meta-isar/recipes-app/example-prebuilt/example-prebuilt_0.1.bb
> > @@ -0,0 +1,23 @@
> > +# Sample recipe to include a prebuilt deb archive into an isar
> > build +#
> > +# This software is a part of ISAR.
> > +
> > +## hacks for the sake of the example
> > +DEPENDS += "${PN}-dummy"
> > +do_fetch[depends] += "${PN}-dummy:do_deploy_deb"
> > +do_fetch[file-checksums] = ""
> > +FILESPATH_prepend :=
> > "${REPO_ISAR_DIR}/${DISTRO}/pool/main/e/${PN}/:"
>
> I think my approach is clearer /wrt not having the need for this here
> - and the companion package.
Agreed, this includes some "magic" that might be hard to maintain. And
that requires the comments of what it "real" and what is "hack"
Was just looking for a way to come up with a deb that will always be
there, without providing a bad example of how such a deb could become
available.
> > +
> > +## start of real example, the below is relevant
> > +
> > +# note the unpack=false
> > +SRC_URI = "file://${PN}_${PV}_${DISTRO_ARCH}.deb;unpack=false"
> > +
> > +inherit dpkg-base
> > +
> > +# in case you have multiple debs or PN does not match
> > +#PROVIDES="foobar blabla"
> > +
> > +do_dpkg_build() {
> > + bbnote "Not building a package"
> > +}
> >
>
> Otherwise, we are on the same page I think. Yours is more verbose in
> several places.
Let us discuss how to improve your approach and NOT MERGE THIS, yes RFC
... REJECT ...
Henning
> Jan
>
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 7821 bytes --]
prev parent reply other threads:[~2021-02-12 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 13:17 Henning Schild
2021-02-12 13:17 ` [PATCH 2/2] doc/user_manual.md: add a section on how to deal with " Henning Schild
2021-02-12 16:39 ` Jan Kiszka
2021-02-12 16:42 ` [PATCH 1/2] meta-isar: add example recipe for deploying " Jan Kiszka
2021-02-12 18:47 ` Henning Schild [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=20210212194727.743b4732@md1za8fc.ad001.siemens.net \
--to=henning.schild@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