All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v5] kernel-devsrc: restructure for out of tree (and on target) module builds
Date: Fri, 16 Nov 2018 15:15:46 +1300	[thread overview]
Message-ID: <2245203.9ONnnPL5vZ@localhost.localdomain> (raw)
In-Reply-To: <1534647044-14420-1-git-send-email-bruce.ashfield@windriver.com>

Hi Bruce

I just came across this the other day and I had one question:

On Sunday, 19 August 2018 2:50:44 PM NZDT Bruce Ashfield wrote:
> The existing kernel-devsrc package starts with a full copy of the kernel
> source and then starts to strip out elements that are not required.
> 
> This results in extra time (I/O) and extra space being taken up in the
> final package. The main purpose of the kernel-devsrc package has been to
> build modules against the running kernel, not to include a full copy of
> the source code for re-building the kernel. The end result was a
> 600M kernel-devsrc package.
> 
> This restructuring of the package uses an approach similar to other
> distros, where the kernel-devsrc package is for building against the
> running kernel and uses a curated set of copied infrastructure, versus
> a mass copy of the entire kernel.
> ...
>  - There is also a symlink from /lib/modules/<version>/source -> build
>    to reserve a spot for a new package that is simply the kernel
>    source. That package is not part of this update.

Did you manage to get to this or is it still planned?

Thanks,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre




  parent reply	other threads:[~2018-11-16  2:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-19  2:50 [PATCH v5] kernel-devsrc: restructure for out of tree (and on target) module builds Bruce Ashfield
2018-08-19 15:36 ` richard.purdie
2018-08-20 13:42   ` Bruce Ashfield
2018-11-16  2:15 ` Paul Eggleton [this message]
2018-11-16  4:18   ` 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=2245203.9ONnnPL5vZ@localhost.localdomain \
    --to=paul.eggleton@linux.intel.com \
    --cc=bruce.ashfield@windriver.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 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.