From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Konrad Scherer <Konrad.Scherer@windriver.com>
Cc: yocto@yoctoproject.org
Subject: Re: [layerindex-web] RFC: layer index docker fixes
Date: Mon, 16 Jul 2018 22:16:55 +0200 [thread overview]
Message-ID: <2410950.gK5fZyVSBj@localhost.localdomain> (raw)
In-Reply-To: <fb724cc6-0424-21e6-614f-abc45f1eb680@windriver.com>
On Monday, 16 July 2018 8:24:53 PM CEST Konrad Scherer wrote:
> On 07/13/2018 03:29 AM, Paul Eggleton wrote:
> > On Thursday, 12 July 2018 10:16:12 PM CEST you wrote:
> >> I just noticed that the image doesn't contain git. Was this
> >> deliberate or an oversight?
> >
> > Ah, no, it wasn't deliberate - perhaps it was there earlier with
> > buildpack-deps? It doesn't appear that we ever explicitly had it in there.
> > I've added it and pushed the branch again.
>
> I recently noticed that if gcc is removed in the 'apt-get purge' step,
> the bitbake sanity checker will fail due to missing 'gcc' when doing a
> layer update.
Hmm, well that's a different problem - those sanity checks shouldn't be
running. We don't need those tools since we're not building anything. I will
have a look into this.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2018-07-16 20:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 16:17 [layerindex-web] RFC: layer index docker fixes Paul Eggleton
2018-07-11 17:03 ` Konrad Scherer
2018-07-12 6:34 ` Paul Eggleton
2018-07-12 20:16 ` Konrad Scherer
2018-07-13 7:29 ` Paul Eggleton
2018-07-16 18:24 ` Konrad Scherer
2018-07-16 20:16 ` Paul Eggleton [this message]
2018-07-17 10:16 ` Paul Eggleton
2018-07-17 14:48 ` Konrad Scherer
2018-08-29 10:46 ` Paul Eggleton
2018-08-29 23:44 ` Paul Eggleton
2018-09-05 12:04 ` Paul Eggleton
2018-10-02 18:45 ` Konrad Scherer
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=2410950.gK5fZyVSBj@localhost.localdomain \
--to=paul.eggleton@linux.intel.com \
--cc=Konrad.Scherer@windriver.com \
--cc=yocto@yoctoproject.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 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.