From: Robert Yang <liezhi.yang@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>,
"Openembedded-core@lists.openembedded.org"
<Openembedded-core@lists.openembedded.org>
Cc: "Brandt, Todd E" <todd.e.brandt@intel.com>,
Koen Kooi <koen@dominion.thruhere.net>,
Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: Re: Packaging kernel sources
Date: Wed, 10 Sep 2014 14:28:52 +0800 [thread overview]
Message-ID: <540FEFA4.6030109@windriver.com> (raw)
In-Reply-To: <D034EC78.A7DD4%dvhart@linux.intel.com>
Good idea, how about use the name linux-source, but add "custom"
in the summary or description.
// Robert
On 09/10/2014 08:42 AM, Darren Hart wrote:
> Hi all,
>
> I'm working on a project which needs to have the full kernel sources
> installed on the target. The kernel-dev package as defined by
> kernel.bbclass is heavily pruned to minimize packaging time and size and
> is intended to enable building of external modules on the target.
>
> Is there an accepted best-practice for how to get the full source packaged
> and installed? I can easily write a new recipe,
> linux-custom-source_git.bb, to install the sources, for example, without
> impacting the packaging time of "virtual/kernel" package.
>
> It would be nice in some respects for it to all come from the same recipe
> though, but I suspect the impact to the common-case where this is not need
> would be far too great.
>
> Koen, I believe you had a solution for this with Angstrom?
>
next prev parent reply other threads:[~2014-09-10 6:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 0:42 Packaging kernel sources Darren Hart
2014-09-10 2:18 ` Koen Kooi
2014-09-10 6:28 ` Robert Yang [this message]
2014-09-10 8:27 ` Richard Purdie
2014-09-10 14:11 ` Bruce Ashfield
2014-09-10 14:24 ` Richard Purdie
2014-09-10 14:42 ` Bruce Ashfield
2014-09-10 15:13 ` Darren Hart
[not found] ` <11E08D716F0541429B7042699DD5C1A170875BAD@FMSMSX103.amr.corp.intel.com>
2014-09-10 16:13 ` Bruce Ashfield
2014-09-10 16:26 ` Peter A. Bigot
2014-10-02 7:25 ` Robert Yang
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=540FEFA4.6030109@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=Openembedded-core@lists.openembedded.org \
--cc=dvhart@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=todd.e.brandt@intel.com \
--cc=tom.zanussi@linux.intel.com \
/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