From: Tim Bird <tim.bird@am.sony.com>
To: Rudolf Streif <rudolf.streif@linux.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: The term Package as used in the YP docs
Date: Fri, 28 Sep 2012 11:56:51 -0700 [thread overview]
Message-ID: <5065F2F3.70209@am.sony.com> (raw)
In-Reply-To: <CA+gsK-qgU=6MHF4T+U1uU1qjVOGBq6pVsbbrTvwZUnYcBeBy=g@mail.gmail.com>
On 09/28/2012 11:44 AM, Rudolf Streif wrote:
> I am not advocating changing the variable names. I know that this is a huge undertaking and prone to many problems. This probably one of the many legacy things people will have to live with and
> understand. In most cases recipe name and version exactly reflect the name and version of the package it is intended to build which to some extend mitigates the issue.
>
> As far as the Terms section in the manuals is concerned, I see that you already changed the describing text for the variables. That's sufficient, I think.
(I answered Scott privately by mistake - here's some feedback on-list)
I'm in favor of mentioning the history somewhere, because the names
do have a 'P' in them, and this is confusing otherwise.
Overall, I think the new wording is worthwhile.
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Workgroup of the Linux Foundation
Senior Staff Engineer, Sony Network Entertainment
=============================
next prev parent reply other threads:[~2012-09-28 18:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 18:14 The term Package as used in the YP docs Rifenbark, Scott M
2012-09-28 18:23 ` Paul Eggleton
2012-09-28 18:27 ` Rifenbark, Scott M
2012-09-28 18:27 ` Rudolf Streif
2012-09-28 18:34 ` Paul Eggleton
2012-09-28 18:37 ` Rifenbark, Scott M
2012-09-28 18:44 ` Rudolf Streif
2012-09-28 18:46 ` Rifenbark, Scott M
2012-09-28 21:40 ` Brian Lloyd
2012-09-28 18:56 ` Tim Bird [this message]
2012-09-28 19:12 ` Trevor Woerner
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=5065F2F3.70209@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=paul.eggleton@linux.intel.com \
--cc=rudolf.streif@linux.com \
--cc=yocto@yoctoproject.org \
/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.