From: <Mikko.Rapeli@bmw.de>
To: <bruce.ashfield@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] kernel.bbclass: allow exporting files from kernel recipes to sysroot
Date: Mon, 24 Sep 2018 13:55:28 +0000 [thread overview]
Message-ID: <20180924135527.GL9430@hiutale> (raw)
In-Reply-To: <CADkTA4O_nCQTD-3UrCqk95HYj=XvjqduaCkUR5d6FKeUyBNPmw@mail.gmail.com>
On Mon, Sep 24, 2018 at 09:48:26AM -0400, Bruce Ashfield wrote:
> On Mon, Sep 24, 2018 at 9:46 AM, Bruce Ashfield
> <bruce.ashfield@gmail.com> wrote:
> > On Mon, Sep 24, 2018 at 9:44 AM, <richard.purdie@linuxfoundation.org> wrote:
> >> On Mon, 2018-09-24 at 13:42 +0000, Mikko.Rapeli@bmw.de wrote:
> >>> On Mon, Sep 24, 2018 at 02:38:36PM +0100, richard.purdie@linuxfoundat
> >>> ion.org wrote:
> >>> > I was replying from the perspective of how this should work in
> >>> > general.
> >>> > I agree that for this to work with a kernel recipe we do need the
> >>> > change that started this thread and that is probably a reasonable
> >>> > thing
> >>> > to do.
> >>>
> >>> Good, then my patch is not going in the wrong direction.
> >>>
> >>> Remaining problem is if file overwrites will be detected or not so
> >>> that
> >>> accidental overrides of files in linux-libc-headers from kernel
> >>> recipes
> >>> should not be possible...
> >>
> >> That is a general problem and the core sstate code shouldn't let that
> >> happen these days so I think that is already covered?
> >
> > Yep, it should be covered. I was just looking for confirmation.
> >
> > Can everyone have a look at:
> >
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=5305
> >
> > And confirm that it can be closed by this .. ? I suggested my approach
> > in that bug, but it
> > never went anywhere at the time.
>
> Sorry for all the email, I hit send a bit too soon.
>
> The only issue that would remain for that bug is that there's no
> standard/default location for those exported extra headers, and it
> is up to the kernel recipe packager to make sure that their recipes
> know where to look for them.
>
> I'm not convinced there has to be a standard location for them, so
> I'll all for closing that old bug.
It would be nice for kernel.bbclass to help creating the custom kernel specific
-dev package with headers, and it would be nice to have a kernel-headers.bbclass
to help users to find them by adding the path to default include paths for
the recipe. And while writing wishlists, would be nice to support multiple
kernel recipes per machine. We forced a second recipe by cloning the
kernel and other bbclasses and added a different prefix...
But I'm ok with my patch and doing other things per recipe for now.
-Mikko
next prev parent reply other threads:[~2018-09-24 13:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 11:49 [PATCH] kernel.bbclass: allow exporting files from kernel recipes to sysroot Mikko Rapeli
2018-09-21 12:38 ` Bruce Ashfield
2018-09-24 7:25 ` Mikko.Rapeli
2018-09-24 12:12 ` Bruce Ashfield
2018-09-24 12:19 ` Mikko.Rapeli
2018-09-24 13:11 ` Richard Purdie
2018-09-24 13:20 ` Mikko.Rapeli
2018-09-24 13:38 ` richard.purdie
2018-09-24 13:42 ` Mikko.Rapeli
2018-09-24 13:44 ` richard.purdie
2018-09-24 13:46 ` Bruce Ashfield
2018-09-24 13:48 ` Bruce Ashfield
2018-09-24 13:55 ` Mikko.Rapeli [this message]
2018-09-24 14:16 ` richard.purdie
2018-09-24 13:43 ` Bruce Ashfield
2018-09-24 13:56 ` richard.purdie
2018-09-24 14:19 ` Mikko.Rapeli
2018-09-24 14:34 ` richard.purdie
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=20180924135527.GL9430@hiutale \
--to=mikko.rapeli@bmw.de \
--cc=bruce.ashfield@gmail.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