Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] manual/faq: add section about why no binary packages
Date: Mon, 6 Jan 2014 13:26:38 +0800	[thread overview]
Message-ID: <20140106132638.39cd986c@skate> (raw)
In-Reply-To: <20140106051625.GD7812@tarshish>

Dear Baruch Siach,

On Mon, 6 Jan 2014 07:16:25 +0200, Baruch Siach wrote:

> Thanks for working on this. I think it is also worth mentioning the rationale. 
> By doing source only we avoid the complexity of handling installation time 
> dependency tracking and resolution. We also don't need to track what files 
> each package installs. This makes Buildroot simpler and easier to work with.

I would go even further, and explain why tracking what files each
package installs is by far not sufficient to support binary packages.
Several people have showed up throughout the project history, willing
to add support binary packages by assuming that simply tracking which
files "make install" installs will be sufficient. But that's forgetting
all the optional dependencies problems, and various other things.

We had a write-up about this in some report of a past Buildroot
Developers Meeting, with some good arguments. Would be nice to dig that
up and summarize these arguments in the doc.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-01-06  5:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-05 20:44 [Buildroot] [RFC] FAQ entry about why no binary packages Yann E. MORIN
2014-01-05 20:44 ` [Buildroot] [PATCH] manual/faq: add section " Yann E. MORIN
2014-01-05 23:49   ` Samuel Martin
2014-01-06  5:16   ` Baruch Siach
2014-01-06  5:26     ` Thomas Petazzoni [this message]
2014-01-28 20:58       ` Thomas Petazzoni
2014-01-06 10:18   ` Thomas De Schampheleire

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=20140106132638.39cd986c@skate \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox