Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] docs/manual: expand on why using a branch name is not supported
Date: Sat, 4 Aug 2018 18:36:44 +0200	[thread overview]
Message-ID: <20180804183644.63b7ec0c@windsurf> (raw)
In-Reply-To: <7f01fc03df91561ce5163e1e300d36f2c642f913.1533400367.git.yann.morin.1998@free.fr>

Hello,

On Sat,  4 Aug 2018 18:33:04 +0200, Yann E. MORIN wrote:

> ++
> +.Note:
> +Using a branch name as +FOO_VERSION+ is not supported, because it does
> +not and can not work as people would expect it should:
> ++
> +  1. Due to local caching, Buildroot will not re-fetch the repository,
> +     so people that expect to be able to follow the remote repository
> +     will be quite surprised and disapointed;

disappointed with two "p"

> +  2. if the user removes the local cache, then the build is no longer
> +     reproducible, because the remote repository may change any time
> +     between two builds, and people will be quite surprised and
> +     disapointed.

Ditto here.

But in fact more importantly than removing the local cache, it means
that between two developers building the same Buildroot configuration,
they won't be building the same state of the source code. I think this
is more important than a user voluntarily removing stuff from its local
cache.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-08-04 16:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-04 16:33 [Buildroot] [PATCH 0/3] download: detect and refuse git branch by name Yann E. MORIN
2018-08-04 16:33 ` [Buildroot] [PATCH 1/3] support/download: remove help from wrapper Yann E. MORIN
2018-08-09 21:48   ` Thomas Petazzoni
2018-08-04 16:33 ` [Buildroot] [PATCH 2/3] docs/manual: expand on why using a branch name is not supported Yann E. MORIN
2018-08-04 16:36   ` Thomas Petazzoni [this message]
2018-08-09 21:48   ` Thomas Petazzoni
2018-08-04 16:33 ` [Buildroot] [PATCH 3/3] support/download: detect and abort when using a git branch by name Yann E. MORIN
2018-08-06  3:14   ` Ricardo Martincoski
2018-08-06 18:36     ` Yann E. MORIN
2018-08-07  0:39       ` Ricardo Martincoski
2018-08-12 20:25         ` Yann E. MORIN
2018-08-12 20:41           ` Thomas Petazzoni
2018-08-12 20:48             ` Yann E. MORIN
2018-08-13 14:13               ` ricardo.martincoski at gmail.com
2018-08-13 16:06                 ` Yann E. MORIN
2018-08-16  1:04                   ` Ricardo Martincoski
2018-08-21 20:22                     ` Arnout Vandecappelle
2018-08-21 23:45                       ` Ricardo Martincoski
2018-08-13 14:33             ` Ricardo Martincoski
2018-08-13 16:19               ` Yann E. MORIN
2018-08-16  3:13                 ` Ricardo Martincoski

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=20180804183644.63b7ec0c@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