Re: [PATCH] meta: add dpkg-prebuilt.bbclass

[Henning Schild <henning.schild@siemens.com>]

Am Fri, 1 Oct 2021 14:25:27 +0200
schrieb "Schmidt, Adriaan (T RDA IOT SES-DE)"
<adriaan.schmidt@siemens.com>:

> > 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.

Yes maybe match that .deb just to be on the safe side, even if people
do not end up mixing.

> > 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.

Sure it is valid. And you can always argue if it should not be more
than one recipe if it does multiple packages. So whoever want to deploy
multiple debs will be on a non-standard path anyways and deal with
PROVIDES and stuff.

Henning

> Adriaan
>