Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Allowing to build from Git branches
Date: Wed, 15 Jan 2020 14:40:48 +0100	[thread overview]
Message-ID: <20200115144048.424279f5@windsurf> (raw)
In-Reply-To: <a299da2b-3b31-d9d3-ebbd-7c67b731ffe7@logilin.fr>

On Wed, 15 Jan 2020 09:54:16 +0100
Christophe Blaess <mailist@logilin.fr> wrote:

> > However, what I am proposing is not going that far. All what I'm
> > proposing is that if you're doing a clean build, if a package points to
> > a Git branch as an upstream source, then Buildroot would re-fetch from
> > that Git branch rather than using a locally cached tarball in DL_DIR
> > potentially corresponding to an older version of that Git branch.  
> 
> Would it be possible to have an option on a per-package basis to always 
> by-pass the DL_DIR mechanism and re-fetch the sources?

Yes, that would definitely be an idea. There was some discussion
yesterday evening about this on IRC with Yann E. Morin, and indeed one
of the idea that came up is to have something like
<pkg>_DOWNLOAD_TRANSIENT = YES, which would tell the download
infrastructure to refetch from upstream everytime the package is built
instead of using a locally available tarball.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-01-15 13:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 21:04 [Buildroot] Allowing to build from Git branches Thomas Petazzoni
2020-01-14 21:10 ` Vincent Fazio
2020-01-14 21:14   ` Michael Nazzareno Trimarchi
2020-01-15  7:07 ` Chris Packham
2020-01-15  8:00   ` Thomas Petazzoni
2020-01-15  8:30     ` Chris Packham
2020-01-15  9:02       ` Nicolas Carrier
2020-01-15  8:54     ` Christophe Blaess
2020-01-15 13:40       ` Thomas Petazzoni [this message]
2020-01-15 20:43         ` Yann E. MORIN
2020-01-15 14:06       ` Adam Duskett

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=20200115144048.424279f5@windsurf \
    --to=thomas.petazzoni@bootlin.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