From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: Phil Blundell <pb@pbcl.net>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] kernel: restore scripts in the sysroot
Date: Tue, 19 Nov 2013 17:48:59 -0500 [thread overview]
Message-ID: <CADkTA4NKP_w_WmWycZwfg6_dYnL7bbOCwT-29J97kqqELKXF0g@mail.gmail.com> (raw)
In-Reply-To: <1384904664.4213.4.camel@x121e.pbcl.net>
On Tue, Nov 19, 2013 at 6:44 PM, Phil Blundell <pb@pbcl.net> wrote:
> On Tue, 2013-11-19 at 17:37 -0500, Bruce Ashfield wrote:
>> Alternatively, recipes need to be fixed to call the
>> modules-base.bbclass routine to restore
>> scripts, and I think it is obvious that won't work in all cases.
>
> Admittedly I'm no expert, but this is not obvious to me. Why can't
> those recipes just be fixed to do the right thing?
Alas, people with legacy build environments that they've wrapped and ported
to bitbake .. they either can't or won't change, so I'm stuck at least trying
to detect them.
That wasn't the primary driver for this though, if that case breaks, they'll
live and so will i :)
I think we are converging to removing the sstate scripts restore, which is
fine with me a this point, as long as Khem isn't broken.
Bruce
>
> p.
>
>
--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
next prev parent reply other threads:[~2013-11-19 22:48 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 21:12 [PATCH 0/1] kernel: restore scripts in the sysroot Bruce Ashfield
2013-10-08 21:12 ` [PATCH 1/1] " Bruce Ashfield
2013-11-19 17:37 ` Mike Crowe
2013-11-19 17:37 ` [PATCH 1/2] kernel.bbclass: Ensure compiler is available for do_populate_sysroot_setscene Mike Crowe
2013-11-19 17:37 ` [PATCH 2/2] kernel.bbclass: Call make with correct variables in kernelscripts_sstate_postinst Mike Crowe
2013-11-19 17:41 ` Bruce Ashfield
2013-11-19 17:46 ` Richard Purdie
2013-11-19 17:56 ` Bruce Ashfield
2013-11-19 17:49 ` Mike Crowe
2013-11-19 17:59 ` Phil Blundell
2013-11-19 17:47 ` [PATCH 1/2] kernel.bbclass: Ensure compiler is available for do_populate_sysroot_setscene Bruce Ashfield
2013-11-19 17:46 ` [PATCH 1/1] kernel: restore scripts in the sysroot Phil Blundell
2013-11-19 17:54 ` Bruce Ashfield
2013-11-19 18:17 ` Bruce Ashfield
2013-11-19 22:29 ` Khem Raj
2013-11-19 22:36 ` Richard Purdie
2013-11-19 22:39 ` Khem Raj
2013-11-19 22:45 ` Richard Purdie
2013-11-20 2:59 ` Khem Raj
2013-11-20 4:43 ` Bruce Ashfield
2013-11-19 22:37 ` Bruce Ashfield
2013-11-19 22:42 ` Richard Purdie
2013-11-19 22:46 ` Bruce Ashfield
2013-11-19 23:44 ` Phil Blundell
2013-11-19 22:48 ` Bruce Ashfield [this message]
2013-11-19 23:41 ` Phil Blundell
-- strict thread matches above, loose matches on Subject: below --
2013-10-04 0:02 [PATCH 0/1] kernel: provide " Bruce Ashfield
2013-10-04 0:02 ` [PATCH 1/1] kernel: restore " Bruce Ashfield
2013-10-04 0:58 ` Khem Raj
2013-10-04 0:59 ` Bruce Ashfield
2013-10-04 7:46 ` Richard Purdie
2013-10-04 12:42 ` Bruce Ashfield
2013-10-04 20:23 ` Khem Raj
2013-10-07 5:02 ` Bruce Ashfield
2013-10-07 9:58 ` Richard Purdie
2013-10-07 15:20 ` Bruce Ashfield
2013-10-07 16:18 ` Richard Purdie
2013-10-07 16:20 ` Bruce Ashfield
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=CADkTA4NKP_w_WmWycZwfg6_dYnL7bbOCwT-29J97kqqELKXF0g@mail.gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.