From: Tim Bird <tim.bird@am.sony.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
Chris Larson <clarson@kergoth.com>
Subject: Re: of recipes and packages
Date: Wed, 22 Aug 2012 16:24:18 -0700 [thread overview]
Message-ID: <50356A22.7070705@am.sony.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1208221623080.20631@oneiric>
On 08/22/2012 01:27 PM, Robert P. J. Day wrote:
> On Wed, 22 Aug 2012, Chris Larson wrote:
>
>> On Wed, Aug 22, 2012 at 1:15 PM, Trevor Woerner <twoerner@gmail.com> wrote:
>>> On Wed, Aug 22, 2012 at 3:24 PM, Chris Larson <clarson@kergoth.com> wrote:
>>>> On Wed, Aug 22, 2012 at 12:23 PM, Trevor Woerner <twoerner@gmail.com> wrote:
>>>>> "bitbake -s" doesn't list "net-snmp-dbg net-snmp-doc net-snmp-dev..."
>>>>> it lists "net-snmp". Therefore couldn't the wording of the bitbake
>>>>> help be improved to say:
>>>>>
>>>>> -s, --show-versions show current and preferred versions of all __recipes__
>>>>>
>>>>> instead of:
>>>>
>>>>
>>>> It could, and should, be changed in that way, yes.
>>>
>>> Do the OE people accept this wording too, or is this a
>>> yocto-project-only thing? In other words, should a potential patch be
>>> sent to OE or here?
>>
>> The change would be to a core component, which is part of OE and which
>> yocto pulls in — bitbake. So it would make no sense to send the patch
>> here. No changes to bitbake are going into poky without going into the
>> main bitbake repository. The bitbake-devel mailing list is the correct
>> place for it.
>
> there really should be an official glossary somewhere, and it should
> be backed up with *actual* *examples* from the source as much as
> possible. that is, don't use "foo" if there's an existing recipe or
> package whose use would be more informative.
From Jeff's description, it sounded like the package (especially 'package version')
comes from the stuff that is the recipe's *input*, and not the recipe's output
-- if you've selected to build packages and not just a straight image.
Is 'package' also used in that sense, to describe, say, the tarball for busybox
before it's processed by bitbake and made into an busybox binary ipkg or rpm?
Or am I just muddying the waters further?
BTW, on denzil, I get the following:
$ bitbake -s | grep busybox
busybox :1.19.4-r2
Note that this includes the version of busybox (the input source version), as
well as (I think) the recipe revision number.
And yes - a definitive glossary would be great.
-- 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-08-22 23:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 17:05 of recipes and packages Trevor Woerner
2012-08-22 17:15 ` Jeff Osier-Mixon
2012-08-22 19:23 ` Trevor Woerner
2012-08-22 19:24 ` Chris Larson
2012-08-22 20:15 ` Trevor Woerner
2012-08-22 20:16 ` Chris Larson
2012-08-22 20:27 ` Robert P. J. Day
2012-08-22 23:24 ` Tim Bird [this message]
2012-08-22 23:25 ` Khem Raj
2012-08-23 7:14 ` Paul Eggleton
2012-08-23 18:02 ` Trevor Woerner
2012-08-23 18:19 ` Chris Larson
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=50356A22.7070705@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=clarson@kergoth.com \
--cc=rpjday@crashcourse.ca \
--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.