Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] manual: add virtual package tutorial.
Date: Tue, 18 Feb 2014 13:03:00 +0100	[thread overview]
Message-ID: <53034BF4.40701@mind.be> (raw)
In-Reply-To: <20140218114448.GB6731@pc-eric>

On 18/02/14 12:44, Eric Le Bihan wrote:
>>  To make it easier for the reader to distinguish between them, perhaps it
>> > would be better to the virtual package V and the provider package P.
> Do you mean using BR2_PACKAGE_HAS_V instead of BR2_PACKAGE_HAS_FOO and so on?
> FOO and BAR/BAZ are already used in other parts of the manual and single
> letter package names look strange to me. They also make a better distinction
> between the prefix of the symbol and the name of the package.

 FOO BAR BAZ are OK to use when the names are meaningless. Here it would
be better if the package name would embed the role that the package plays
in the explanation. But I admit that V and P are a bit short. I wanted to
avoid VIRTUAL and PROVIDER because that sounds too much as if that prefix
is part of the infrastructure.

 Maybe something-virtual and some-provider.

 Regards,
 Arnout

-- 
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

  reply	other threads:[~2014-02-18 12:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14 15:11 [Buildroot] [PATCH v2 1/1] manual: add virtual package tutorial Eric Le Bihan
2014-02-17 17:19 ` Arnout Vandecappelle
2014-02-18 11:44   ` Eric Le Bihan
2014-02-18 12:03     ` Arnout Vandecappelle [this message]
2014-02-18 20:34 ` Samuel Martin
2014-02-19 14:19   ` Eric Le Bihan
2014-02-23 19:04     ` Yann E. MORIN
2014-02-24 10:00       ` Eric Le Bihan

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=53034BF4.40701@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