Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] BR2_REPRODUCIBLE issues
Date: Mon, 06 Nov 2017 21:39:07 +0100	[thread overview]
Message-ID: <87d14vw39w.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20171106175012.GA2763@scaer> (Yann E. MORIN's message of "Mon, 6 Nov 2017 18:50:12 +0100")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

Hi,

 > I do see your use case, and I do understand it: you basically want to do
 > partial upgrades of your system (for various reasons that are your own
 > right).

 > But Buildroot does not build packages like a distro, like OpenEmbedded
 > or like openWRT (or others) do.

 > Instead, Buildroot builds a complete rootfs; it is the atomic artefact
 > output by Buildroot. As such, what matters for Buildroot is the whole,
 > not the parts.

 > See also the manual, where we explain at length why we are not doing
 > binary packages, especially the last part about our position statement,
 > tangentially related to the explanation of your use-case:
 >     https://buildroot.org/downloads/manual/manual.html#faq-no-binary-packages

Small deltas might be interesting even though you do full system
upgrades, E.G. to save on bandwidth with binary delta tools like xdelta/bsdiff
or casync. I believe there was some talk about adding casync support to
rauc.

 > Sorry if you found my and the others' replies to imply that you should
 > "shut up". That was definitely not my intention, and I know Peter,
 > Arnout and Thomas enough to know that it was not theirs as well.

Exactly!

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2017-11-06 20:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-03 14:40 [Buildroot] BR2_REPRODUCIBLE issues Einar Jón Gunnarsson
2017-11-03 20:15 ` Peter Korsgaard
2017-11-04 19:53   ` Arnout Vandecappelle
2017-11-04 20:49     ` Peter Korsgaard
2017-11-04 22:24     ` Thomas Petazzoni
2017-11-05  8:46     ` Yann E. MORIN
2017-11-06  9:43       ` Einar Jón
2017-11-06 17:50         ` Yann E. MORIN
2017-11-06 20:39           ` Peter Korsgaard [this message]
2017-11-06 22:50           ` Arnout Vandecappelle
2017-11-08 18:00             ` Yann E. MORIN
2017-11-08 18:59               ` Peter Korsgaard
2017-11-08 22:07               ` Arnout Vandecappelle
2017-11-06 21:34         ` Arnout Vandecappelle
2017-11-06 21:37           ` Yann E. MORIN
2017-11-05  8:35 ` Yann E. MORIN
2017-11-05  8:54   ` Peter Korsgaard
2017-11-05  8:59     ` 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=87d14vw39w.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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