From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: Add CIP SLTS easy selection option
Date: Sat, 4 Mar 2017 15:12:28 +0100 [thread overview]
Message-ID: <20170304151228.3de59a5c@free-electrons.com> (raw)
In-Reply-To: <CA+TH9VkMUTq7sFR9ED9aLgwUCbnnkXyO5uS7fwTyb5CynW2=bg@mail.gmail.com>
Hello,
On Sat, 4 Mar 2017 15:08:06 +0100, Angelo Compagnucci wrote:
> > Note that the original patch did have a few issues:
> > - It should use a tag/sha rather than a branch;
>
> Using a tag/sha will defeat the purpose of using this kernel. A
> developer should ever use the latest release of this kernel each time
> he compiles a buildroot image.
Clearly *NOT*. We want Buildroot builds to be reproducible. So if you
take a given Buildroot version and configuration, it should *always*
provide exactly the same output. So we need to use fixed versions of
all the components.
Doing otherwise would be absolutely horrible. You do a build one day,
it works. The next day, your colleague takes your Buildroot version and
configuration, does a build, and the build fails? Or the build works,
but it no longer boots/works on the target?
So no, we clearly do not want this to use the "latest release each time
a Buildroot image is compiled".
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-04 14:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-03 21:50 [Buildroot] [PATCH] linux: Add CIP SLTS easy selection option Angelo Compagnucci
2017-03-03 22:46 ` Thomas Petazzoni
2017-03-03 22:50 ` Arnout Vandecappelle
2017-03-03 23:02 ` Thomas Petazzoni
2017-03-03 23:43 ` Arnout Vandecappelle
2017-03-04 10:11 ` Thomas Petazzoni
2017-03-04 11:31 ` Angelo Compagnucci
2017-03-04 12:17 ` Arnout Vandecappelle
2017-03-04 14:08 ` Angelo Compagnucci
2017-03-04 14:12 ` Thomas Petazzoni [this message]
2017-03-04 14:38 ` Angelo Compagnucci
2017-03-04 14:42 ` Thomas Petazzoni
2017-03-04 15:07 ` Angelo Compagnucci
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=20170304151228.3de59a5c@free-electrons.com \
--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.