From: "Cliff Brake" <cliff.brake@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [doc] defining OpenEmbedded
Date: Wed, 24 Oct 2007 07:01:30 -0400 [thread overview]
Message-ID: <f96d234e0710240401o7fcdae32qc7d43ef162f38744@mail.gmail.com> (raw)
In-Reply-To: <20071024095844.GA9952@lenovo>
On 10/24/07, David Farning <dfarning@gmail.com> wrote:
> Getting started is coming along nicely.
Great!
> In the second case referring to OE as a collection of metadata is
> confusing. Metadata is data about the data. OE is actually a
> collection of patches, task lists, and configuration files. I was
> wondering if it would be more clear to refer to oe as either a ruleset
> or task lists.
The term metadistribution seems to be somewhat accepted:
http://gentoo-wiki.com/Metadistribution
In the most basic sense, a bitbake recipe is data about data (the
source that needs built), so I think the term fits. Just my opinion.
Cliff
--
=======================
Cliff Brake
http://bec-systems.com
next prev parent reply other threads:[~2007-10-24 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 9:58 [doc] defining OpenEmbedded David Farning
2007-10-24 10:47 ` Michael Krelin
2007-10-24 10:51 ` Marcin Juszkiewicz
2007-10-24 11:01 ` Cliff Brake [this message]
2007-10-24 15:36 ` David Farning
2007-10-24 17:11 ` Koen Kooi
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=f96d234e0710240401o7fcdae32qc7d43ef162f38744@mail.gmail.com \
--to=cliff.brake@gmail.com \
--cc=openembedded-devel@lists.openembedded.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.