Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] cached downloads for scm branches
Date: Thu, 20 Oct 2016 21:45:51 +0200	[thread overview]
Message-ID: <20161020194551.GA3372@free.fr> (raw)
In-Reply-To: <f006d88783fb1d99aaef2d6cab1dfc88@walle.cc>

Michael, All,

On 2016-10-20 19:27 +0200, Michael Walle spake thusly:
> Hi,
> 
> If I have a package which downloads it's source from a SCM branch, the
> download will be cached in DL_DIR/<pkgname>-<branchname>.tar.gz. This makes
> sense if the version is a tag or a (git) hash. But if used with branches,
> the package will never be downloaded again until I remove it from the
> DL_DIR. This may be the intended behaviour, but as far as I can tell, I have
> no chance to change it.

Yes, this is the intended behaviour: you should not use a branch names
or other unstable references Using a branch name makes the build
non-reproducible, and that is not good.

Only use stable references, like a tag or a sha1 or ...

If however you are actively working on the package, then you should use
the source-override mechanism instead:

  - create a local.mk file (in the directory where you ran 'make
    menuconfig')

  - in that file, add this line

        MY_PACKAGE_OVERRIDE_SRCDIR = /path/to/my-package

Then you can manage that location "by hand" (like pulling new changes...)
and have it automatically used by Buildroot:

    make my-package-rebuild

(and other such commands, see "make help" and the manual for the
complete set.)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

      parent reply	other threads:[~2016-10-20 19:45 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
2016-10-21 18:09     ` Arnout Vandecappelle
2016-10-20 19:45 ` Yann E. MORIN [this message]

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=20161020194551.GA3372@free.fr \
    --to=yann.morin.1998@free.fr \
    --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