From: Robert Schwebel <r.schwebel@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] Kernel: never provide a development prebuild package
Date: Tue, 21 Jan 2014 13:00:44 +0100 [thread overview]
Message-ID: <20140121120044.GJ12605@pengutronix.de> (raw)
In-Reply-To: <201401211259.55399.jbe@pengutronix.de>
On Tue, Jan 21, 2014 at 12:59:55PM +0100, Juergen Beisert wrote:
> Even if the developer enables the usage of prebuild packages, the Linux kernel
> should not be part of it. The kernel is a too sensitive part and its build must
> always be forced.
>
> Signed-off-by: Juergen Beisert <jbe@pengutronix.de>
> ---
> diff --git a/rules/kernel.make b/rules/kernel.make
> index 8301b83..f4b3990 100644
> --- a/rules/kernel.make
> +++ b/rules/kernel.make
> @@ -37,6 +37,7 @@ KERNEL_CONFIG := $(call remove_quotes, $(PTXDIST_PLATFORMCONFIGDIR)/$(PTXCONF_K
> KERNEL_LICENSE := GPLv2
> KERNEL_URL := $(call kernel-url, KERNEL)
> KERNEL_SOURCE := $(SRCDIR)/$(KERNEL).$(KERNEL_SUFFIX)
> +KERNEL_DEVPKG := NO
>
> # ----------------------------------------------------------------------------
> # Prepare
The idea of the devpkg mechanism is to build everything beforehand. A
standard usecase is that one team prepares a system and another one does
already care about the application. So it would be helpful to have also
the kernel pre-built.
Can you elaborate what kind of issue you have seen?
rsc
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2014-01-21 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 11:59 Juergen Beisert
2014-01-21 12:00 ` Robert Schwebel [this message]
2014-01-21 13:22 ` Michael Olbrich
2014-01-21 13:29 ` Juergen Beisert
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=20140121120044.GJ12605@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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