From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Diego Sueiro <Diego.Sueiro@arm.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 1/2] classes: Introduce intermediate-deploy.bbclass
Date: Thu, 14 Jan 2021 13:27:33 +0000 [thread overview]
Message-ID: <ce613531685e040d039bceba3bad99bf60c5d7aa.camel@linuxfoundation.org> (raw)
In-Reply-To: <AM6PR08MB3461D404A67176C477DE723E92A80@AM6PR08MB3461.eurprd08.prod.outlook.com>
On Thu, 2021-01-14 at 13:06 +0000, Diego Sueiro wrote:
>
> Just trying to see if I got it right this time.
> Are you proposing to move `${D}/boot` to `${D}/intermediate-
> deploy/boot` and
> have SYSROOT_DIRS += "/intermediate-deploy "?
Yes.
> But, If it is just a copy having within ${D} , I'll have to have
> `PACKAGES_${PN} += "${PN}-intermediate-deploy"` and
> FILES_${PN}-intermediate-deploy = "/intermediate-deploy" to no fail
> with "installed-vs-shipped" in the package qa.
Or, we have perform_packagecopy() just delete/skip it. That would mean
it won't make it into the packages.
(we could also implement as a PACKAGE_PREPROCESS_FUNC but I'd probably
just add to the above function instead?)
> The way this class is implemented is just copying the dirs from $D
> listed in
> $INTERMEDIATE_DEPLOY_DIRS to the $SYSROOT_DESTDIR and can't use
> SYSROOT_DIRS
> variable directly because the sysroot_stage_all function copies from
> $D.
>
>
> > I'm not particularly liking the name. Maybe "unpackaged/boot" or
> > "non-
> > target/boot"? I'm open to ideas.
> >
> > The idea is to make it really clear these are files which are not
> > part of the
> > target rootfs though...
>
> I also don’t like this name either. Maybe "non-filesystem/boot"?
Maybe sysroot-only/boot/ ?
Cheers,
Richard
prev parent reply other threads:[~2021-01-14 13:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 8:06 [PATCH 1/2] classes: Introduce intermediate-deploy.bbclass Diego Sueiro
2021-01-14 8:06 ` [PATCH 2/2] u-boot: Use intermediate-deploy.bbclass to share artifacts Diego Sueiro
2021-01-14 11:56 ` [OE-core] [PATCH 1/2] classes: Introduce intermediate-deploy.bbclass Otavio Salvador
2021-01-14 12:45 ` Diego Sueiro
2021-01-14 15:32 ` Christopher Larson
2021-01-14 12:04 ` Richard Purdie
2021-01-14 13:06 ` [OE-core] " Diego Sueiro
2021-01-14 13:27 ` Richard Purdie [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=ce613531685e040d039bceba3bad99bf60c5d7aa.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Diego.Sueiro@arm.com \
--cc=openembedded-core@lists.openembedded.org \
/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