From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] manual/faq: add section about why no binary packages
Date: Tue, 18 Feb 2014 00:01:22 +0100 [thread overview]
Message-ID: <530294C2.40400@mind.be> (raw)
In-Reply-To: <CANxTyt5-j5636R=1KY5uNyvEDRHHwUNz76VaaeMjjK67Qw8OTw@mail.gmail.com>
On 17/02/14 23:48, Danomi Manchego wrote:
> Yann,
>
> On Mon, Feb 17, 2014 at 4:37 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
>> > Danomi, All,
>> >
>> > On 2014-02-17 15:21 -0500, Danomi Manchego spake thusly:
>>> >> Nit-picky writing editorial - no issue with the actual content ...
>> >
>> > Thank you!
>> >
>> > My answers below...
>> >
>>> >> On Mon, Feb 17, 2014 at 12:52 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
>> > [--SNIP--]
>>>> >> > +[[faq-no-binary-packages]]
>>>> >> > +Why doesn't Buildroot generate binary packages (.deb, .ipkg...)?
>>>> >> > +----------------------------------------------------------------
>>>> >> > +
>>>> >> > +One feature that is often discussed on the Buildroot list, is the
>>> >>
>>> >> no comma
>> >
>> > Fixed.
>> >
>>>> >> > +the general topic of "package management". To summarize, the idea
>>>> >> > +would be to add some tracking of which Buildroot package installs
>>>> >> > +what files, with the goals of:
>>>> >> > +
>>>> >> > + * Being able to remove files installed by a package when this package
>>>> >> > + gets unselected from the menuconfig ;
>>> >>
>>> >> ; -> .
> It seems strange to me that a bulleted list is also considered a
> complete sentence. I think of bulleted lists like an unsorted list of
> items, as opposed to a numbered list where numbers have meaning. But
> it's your party, keep as you like.
If you have a colon in front of it and a semicolon at the end, then the
sentence shouldn't be capitalized. So:
with the goals of:
* being able to remove files;
* being able to do the other thing.
Regards,
Arnout
[snip]
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-02-17 23:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 17:52 [Buildroot] [PATCH 0/1 v2] FAQ entry about why no binary packages Yann E. MORIN
2014-02-17 17:52 ` [Buildroot] [PATCH 1/1] manual/faq: add section " 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 [this message]
2014-02-18 20:14 ` Samuel Martin
2014-02-18 20:37 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2014-02-20 17:01 [Buildroot] [PATCH 0/1 v3] FAQ entry " Yann E. MORIN
2014-02-20 17:01 ` [Buildroot] [PATCH 1/1] manual/faq: add section " Yann E. MORIN
2014-02-20 21:19 ` Peter Korsgaard
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=530294C2.40400@mind.be \
--to=arnout@mind.be \
--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