From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] barebox: add support for custom version, tarball, git and patch dir
Date: Fri, 23 Sep 2011 09:49:14 +0200 [thread overview]
Message-ID: <20110923094914.5c13b978@skate> (raw)
In-Reply-To: <201109222145.19265.arnout@mind.be>
Le Thu, 22 Sep 2011 21:45:19 +0200,
Arnout Vandecappelle <arnout@mind.be> a ?crit :
> Since I have a separate branch or even repository per project, yes I put them
> directly into the package directories. But I realize this is not necessarily
> the best way to work.
I don't think there "a best way" to work, but I think that for highly
hardware-dependent packages such as bootloaders and kernel, it makes
sense to offer some options to apply additional patches.
Note that this option not only supports a local directory, but also the
URL of a patch, or the URL of a tarball containing patches. This can be
very useful for hardware manufacturers who want to ship a Buildroot
environment with a proper configuration. They can just do a config that
says:
* Use Linux 3.0
* Use Linux patches available at
http://foobar.com/linux-3.0-my-patches.tar.bz2
* Use U-Boot 2011.09
* Use U-Boot patches available at
http://foobar.com/u-boot-2001.09-my-patches.tar.bz2
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:[~2011-09-23 7:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-17 20:23 [Buildroot] [PATCH] barebox: add support for custom version, tarball, git and patch dir Jean-Christophe PLAGNIOL-VILLARD
2011-09-18 20:06 ` Peter Korsgaard
2011-09-22 17:20 ` Arnout Vandecappelle
2011-09-22 18:57 ` Thomas Petazzoni
2011-09-22 19:45 ` Arnout Vandecappelle
2011-09-23 7:49 ` Thomas Petazzoni [this message]
2011-09-22 19:55 ` Peter Korsgaard
2011-09-23 6:27 ` Thomas De Schampheleire
2011-09-23 7:55 ` 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=20110923094914.5c13b978@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 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.