From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: The term Package as used in the YP docs
Date: Fri, 28 Sep 2012 19:23:28 +0100 [thread overview]
Message-ID: <23679865.otXK9bZ5Ws@helios> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A720D0@FMSMSX151.amr.corp.intel.com>
Hi Scott,
On Friday 28 September 2012 18:14:31 Rifenbark, Scott M wrote:
> * Package: In the context of the Yocto Project, this term refers to
> the packaged output from a baked recipe. A package is generally the
> compiled binaries produced from the recipe's sources. You 'bake' something
> by running it through BitBake.
>
> It is worth noting that the term "package" can, in general, have subtle
> meanings. For example, the packages refered to in the "The
> Packages<http://www.yoctoproject.org/docs/1.3/yocto-project-qs/yocto-projec
> t-qs.html#packages>" section are compiled binaries that when installed add
> functionality to your Linux distribution.
The thing is, this is actually the same meaning, we're just talking about
packages for your host distribution rather than packages for the custom distro
you're building - the concept is the same. If we do need to clarify it I would
suggest using the term "host package" or something very similar for packages
to be installed as pre-requisites on the host system.
> Another point worth noting is that historically within the Yocto Project,
> recipes were referred to as packages - thus, the existence of several
> BitBake variables that are seemingly mis-named, (e.g.
> PR<http://www.yoctoproject.org/docs/1.3/poky-ref-manual/poky-ref-manual.htm
> l#var-PR>,
> PRINC<http://www.yoctoproject.org/docs/1.3/poky-ref-manual/poky-ref-manual.
> html#var-PRINC>,
> PV<http://www.yoctoproject.org/docs/1.3/poky-ref-manual/poky-ref-manual.htm
> l#var-PV>, and
> PE<http://www.yoctoproject.org/docs/1.3/poky-ref-manual/poky-ref-manual.htm
> l#var-PE>).
I have to say, whilst this is an interesting point of history, I'm not sure
anyone really needs to know this in the manual, particularly if we've replaced
all historical use of the word "package" when we mean "recipe" (as I think we
now have for this release).
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-09-28 18:23 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 [this message]
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
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=23679865.otXK9bZ5Ws@helios \
--to=paul.eggleton@linux.intel.com \
--cc=scott.m.rifenbark@intel.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.