public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>
To: "Schild, Henning (T RDA IOT SES-DE)" <henning.schild@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: RE: [PATCH] meta: add dpkg-prebuilt.bbclass
Date: Fri, 1 Oct 2021 12:25:27 +0000	[thread overview]
Message-ID: <AM4PR1001MB12204530BAF3C3CFA83E3C7AEDAB9@AM4PR1001MB1220.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20210922095416.46f889d9@md1za8fc.ad001.siemens.net>

> From: Henning Schild <henning.schild@siemens.com>
> Sent: Mittwoch, 22. September 2021 09:54
> Subject: Re: [PATCH] meta: add dpkg-prebuilt.bbclass
> 
> I am not sure about the magic unpack prepend. I guess if someone want to
> download more stuff they will have to ";unpack=true" to get back to the
> global default.

I guess it's possible to only append ;unpack=false to *.deb sources, but the more important issue that would break "mixed" recipes is removing all tasks between do_unpack and do_deploy_deb.

> It used to be just "a pattern" that could be easily mixed. Being a class
> deleting tasks and messing with SRC_URI is problematic for such mix recipes.
> But in fact one can keep using the "pattern" and not use the class.

It's true that this is not suited for "mixed" recipes that need to build a package and add a prebuilt deb. In that case you would stick to the "pattern" (and probably don't turn do_dpkg_build into a nop).

This proposal covers "inject an existing deb" only, but makes that task as simple as possible.

Adriaan


  reply	other threads:[~2021-10-01 12:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-21  7:53 Adriaan Schmidt
2021-09-22  7:54 ` Henning Schild
2021-10-01 12:25   ` Schmidt, Adriaan [this message]
2021-10-04 11:07     ` Henning Schild
2021-10-15 15:42 ` Anton Mikanovich

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=AM4PR1001MB12204530BAF3C3CFA83E3C7AEDAB9@AM4PR1001MB1220.EURPRD10.PROD.OUTLOOK.COM \
    --to=adriaan.schmidt@siemens.com \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.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