[Buildroot] [PATCH] manual/faq: add section about why no binary packages

Thomas De Schampheleire patrickdepinguin at gmail.com
Mon Jan 6 10:18:42 UTC 2014


On Sun, Jan 5, 2014 at 9:44 PM, Yann E. MORIN <yann.morin.1998 at free.fr> wrote:
> From: "Yann E. MORIN" <yann.morin.1998 at free.fr>
>
> It somes up evry now and then on the list, so better be prepared to
> point at the manual, rather than rehash the same evry time.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998 at free.fr>
> Cc: Samuel Martin <s.martin49 at gmail.com>
> Cc: Peter Korsgaard <jacmet at uclibc.org>
> Cc: Arnout Vandecappelle <arnout at mind.be>
> Cc: Thomas Petazzoni <thomas.petazzoni at free-electrons.com>
> Cc: Thomas De Schampheleire <patrickdepinguin at gmail.com>
> ---
>  docs/manual/faq-troubleshooting.txt | 21 +++++++++++++++++++++
>  1 file changed, 21 insertions(+)
>
> diff --git a/docs/manual/faq-troubleshooting.txt b/docs/manual/faq-troubleshooting.txt
> index 4e0612b..e97457a 100644
> --- a/docs/manual/faq-troubleshooting.txt
> +++ b/docs/manual/faq-troubleshooting.txt
> @@ -111,3 +111,24 @@ directory as the new root, will most likely fail.
>  If you want to run the target filesystem inside a chroot, or as an NFS
>  root, then use the tarball image generated in +images/+ and extract it
>  as root.
> +
> +[[faq-no-binary-packages]]
> +Why doesn't Buildroot generate binary packages (.deb, .ipkg...)?
> +----------------------------------------------------------------
> +
> +Buildroot explicitly avoids generating binary packages, on purpose.
> +
> +Buildroot strive at making it easy to generate a root filesystem (hence

strives

> +the name, by the way). That is what we want to make Buildroot good at:
> +building root filesystems.
> +
> +Buildroot is not meant to be a distribution (or rather, a distribution
> +generator). It is the opinion of most Buildroot developpers (me included)

developers

> +that this is not a goal we should pursue. We believe that there are other
> +tools better suited to generate a distro than Buildroot is. For example,
> +http://openembedded.org/[Open Embedded], or https://openwrt.org/[openWRT],
> +are such tools.
> +
> +Rather, we prefer to push Buildroot in a direction that makes it easy
> +(or even easier) to generate complete root filesystems. This is what
> +makes Buildroot stands out in the crowd (among other things, of course!).

Best regards,
Thomas



More information about the buildroot mailing list