From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: add option to get sources from custom directory
Date: Wed, 12 Dec 2012 10:54:18 +0100 [thread overview]
Message-ID: <20121212105418.601702fc@skate> (raw)
In-Reply-To: <1354873604-4304-1-git-send-email-rbraun@sceen.net>
Dear Richard Braun,
On Fri, 7 Dec 2012 10:46:44 +0100, Richard Braun wrote:
> diff --git a/linux/Config.in b/linux/Config.in
> index ef3b2a1..cafbe59 100644
> --- a/linux/Config.in
> +++ b/linux/Config.in
> @@ -46,6 +46,12 @@ config BR2_LINUX_KERNEL_CUSTOM_TARBALL
> This option allows to specify the http or ftp location of a
> specific kernel source tarball
>
> +config BR2_LINUX_KERNEL_CUSTOM_DIRECTORY
> + bool "Custom directory"
> + help
> + This option allows to specify the path of a specific kernel
> + source directory.
> +
This duplicates what the "source override" mechanism allows to do in a
generic way for all packages. So on one side, I'm tempted to say "no"
because I don't think it's worth having two mechanisms to achieve the
same thing, especially when the new mechanism is package-specific (what
if someone wants a custom source directory for Qt, for zlib, for
libpng, etc.).
On the other side, Linux, and bootloaders, are kind of special packages
in that very often people will have to work on them, and making this
easier might be useful.
Generally speaking, I'd like us to have an overall "vision" of how to
do development with Buildroot, rather than doing local hacks/fixes per
package to adjust one particular development workflow, which would end
up with many different hacks in various places with absolutely no
coherency.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-12-12 9:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 9:46 [Buildroot] [PATCH] linux: add option to get sources from custom directory Richard Braun
2012-12-12 9:46 ` Richard Braun
2012-12-12 9:54 ` Thomas Petazzoni [this message]
2012-12-12 10:14 ` Richard Braun
2012-12-18 17:40 ` Arnout Vandecappelle
2013-02-14 14:32 ` Richard Braun
2013-02-14 14:46 ` Thomas Petazzoni
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=20121212105418.601702fc@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox