From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH RFC] Revert "Added local directory as source of kernel code"
Date: Mon, 12 Dec 2016 18:52:11 +0100 [thread overview]
Message-ID: <20161212185211.41d61776@free-electrons.com> (raw)
In-Reply-To: <20161212173527.GC3509@free.fr>
Hello,
On Mon, 12 Dec 2016 18:35:27 +0100, Yann E. MORIN wrote:
> But what I want is to be able to use local sources fior Qt5 that I
> prepare for my board; so I'll want to add the same feature for Qt5.
> Then Thomas will want to use local sources for barebox; so he'll want to
> add the same feature for barebox. Then Peter will need it for whatever,
> so he'll want to add it for that as well...
One could however say (with good reason) that the Linux kernel, and a
few other HW-related packages (bootloaders) are special.
And indeed, for those packages (Linux, U-Boot, Barebox, etc.), we do
support fetching from custom Git/Mercurial/etc. repositories. But we
would never do that for *all* packages.
So Linux is already special compared to other packages in that respect,
and this argument could be used (and in fact was used) to add a feature
like BR2_LINUX_KERNEL_CUSTOM_LOCAL_PATH.
But as I said, I don't really feel very strongly about this.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-12-12 17:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-27 22:34 [Buildroot] [PATCH RFC] Revert "Added local directory as source of kernel code" Yann E. MORIN
2016-08-27 20:23 ` Thomas Petazzoni
2016-08-27 22:54 ` Yann E. MORIN
2016-08-28 7:23 ` Thomas Petazzoni
2016-08-28 20:37 ` Peter Korsgaard
2016-08-28 21:48 ` Yann E. MORIN
2016-08-29 7:16 ` Thomas Petazzoni
2016-12-12 3:06 ` James Knight
2016-12-12 16:27 ` Thomas Petazzoni
2016-12-12 17:35 ` Yann E. MORIN
2016-12-12 17:52 ` Thomas Petazzoni [this message]
2016-12-12 22:31 ` James Knight
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=20161212185211.41d61776@free-electrons.com \
--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