All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] cached downloads for scm branches
Date: Fri, 21 Oct 2016 13:46:35 +0200	[thread overview]
Message-ID: <18938922.pbxtG6M13H@sagittea> (raw)
In-Reply-To: <D2934D97-E0A4-4AE5-933C-49D38BFFB436@walle.cc>

Hello Michael,

On Thursday 20 October 2016 22:29:15 Michael Walle wrote:
> hi,
> 
> thanks. yeah i thought so. Just to give you some background regarding
> my question. We have some kind of CI, actually it's rather a daily
> build. we build a root filesystem with some fixed packages, but also
> with multiple packages of our own and we want to track the tip of a
> branch for a build (because it is CI ;)). I don't think the src
> override method really suit the CI case. I guess one way could be
> that the CI defines the commit that should be build. Or simply delete
> the download. mhh ;)

I suggest to pass package version to command line:

  make MY_PKG_VERSION=$(git ls-remote http://repo.git/path master) all

You may also force versions using local.mk:

  override MY_PKG_VERSION = $(shell git ls-remote http://repo.git/path 
master)

However, these ways are not officially supported. Consider them
as hacks.

BR,

-- 
J?r?me Pouiller

  reply	other threads:[~2016-10-21 11:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-20 17:27 [Buildroot] cached downloads for scm branches Michael Walle
2016-10-20 19:38 ` Thomas Petazzoni
2016-10-20 20:29   ` Michael Walle
2016-10-21 11:46     ` Jérôme Pouiller [this message]
2016-10-21 18:09     ` Arnout Vandecappelle
2016-10-20 19:45 ` Yann E. MORIN

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=18938922.pbxtG6M13H@sagittea \
    --to=jezz@sysmic.org \
    --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.