From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/1 v2] FAQ entry about why no binary packages
Date: Mon, 17 Feb 2014 18:52:08 +0100 [thread overview]
Message-ID: <cover.1392659250.git.yann.morin.1998@free.fr> (raw)
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
Hello All!
Every now and then, someone will ask why Buildroot has no support for
generating binary packages.
Rather than re-hash the same answer every time, the following patch
adds a section in the FAQ in the manual, that we can point users to.
The patch is two-fold:
- first, a (slightly tweaked) copy-paste of the report of a Developpers
Day we had in Pragues, in 2011,
- second, a position statement about the issue.
The position statement might be a bit strong in its wordings, so I would
very much appreciate comments about that.
Changes v1 -> v2:
- copy the report from the DevDay (Thomas P)
Regards,
Yann E. MORIN.
----------------------------------------------------------------
Yann E. MORIN (1):
manual/faq: add section about why no binary packages
docs/manual/faq-troubleshooting.txt | 91 +++++++++++++++++++++++++++++++++++++
1 file changed, 91 insertions(+)
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next reply other threads:[~2014-02-17 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 17:52 Yann E. MORIN [this message]
2014-02-17 17:52 ` [Buildroot] [PATCH 1/1] manual/faq: add section about why no binary packages Yann E. MORIN
2014-02-17 20:21 ` Danomi Manchego
2014-02-17 21:37 ` Yann E. MORIN
2014-02-17 22:48 ` Danomi Manchego
2014-02-17 23:01 ` Arnout Vandecappelle
2014-02-18 20:14 ` Samuel Martin
2014-02-18 20:37 ` Thomas Petazzoni
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=cover.1392659250.git.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--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.