From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] package: Redownload HEAD packages every build
Date: Wed, 2 Oct 2013 09:13:49 +0200 [thread overview]
Message-ID: <20131002091349.652d110c@skate> (raw)
In-Reply-To: <OFB02446AE.7536F58C-ON86257BF7.007705C1-86257BF7.00784F1A@rockwellcollins.com>
Dear Ryan Barnett,
On Tue, 1 Oct 2013 16:54:04 -0500, Ryan Barnett wrote:
> > Buildroot will rsync again the source code, and restart the build at
> > the configuration step, or the build step of the foo package.
> >
> > Usually, /path/to/foo/sources/ will be the directory where you did your
> > Subversion checkout or Git clone of your "foo" source code.
>
> Could you add this explanation to buildroot manual since it looks like
> <pkg>_OVERRIDE_SRCDIR mechanism is your feature and it is currently
> lacking in documentation in the manual? I too have tried to understand
> how this feature worked and it was a bit unclear.
>
> The only mention of OVERRIDE_SRCDIR in the documentation is under the
> rebuild and reconfigure commands. Where is says that it that it only
> makes sense to use these features with OVERRIDE_SRCDIR but doesn't
> explain what you just explained above.
Right, I will submit a documentation patch.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-02 7:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 14:43 [Buildroot] [RFC] package: Redownload HEAD packages every build Clayton Shotwell
2013-09-27 14:51 ` Clayton Shotwell
2013-09-27 15:11 ` Thomas De Schampheleire
2013-10-01 16:08 ` Arnout Vandecappelle
2013-10-01 18:51 ` Thomas Petazzoni
2013-10-01 20:01 ` clshotwe at rockwellcollins.com
2013-10-01 21:37 ` Thomas Petazzoni
2013-10-01 21:54 ` Ryan Barnett
2013-10-02 7:13 ` Thomas Petazzoni [this message]
2013-10-02 18:34 ` clshotwe at rockwellcollins.com
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=20131002091349.652d110c@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.