From: Koen Kooi <k.kooi@student.utwente.nl>
To: Using the OpenEmbedded metadata to build Distributions
<openembedded-devel@openembedded.org>
Subject: Re: [doc] defining OpenEmbedded
Date: Wed, 24 Oct 2007 19:11:37 +0200 [thread overview]
Message-ID: <471F7CC9.3060904@student.utwente.nl> (raw)
In-Reply-To: <20071024153620.GA6691@lenovo>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
David Farning schreef:
> On Wed, Oct 24, 2007 at 07:01:30AM -0400, Cliff Brake wrote:
>> 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.
>
> I like metadistribution. Metadistribution is a term referring to an
> adaptable system that is capable of building itself to the user's
> specification.
The reason we tend to avoid the term 'distribution' is because OE is
cabable of building multiple distributions (you could make OE build a
1:1 copy of the fedora install DVD if you want), instead of building
only a single distro for multiple archs.
I agree metadistro covers what OE is, but it is also the most confusing
name to people unfamiliar with OE.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFHH3zJMkyGM64RGpERAtoaAJ4lXq5RC0FYVieAWP9O8nrQHnmtBgCgubME
QNzwmMEMBP3we92c5HFoogA=
=ni1H
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2007-10-24 17:18 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
2007-10-24 15:36 ` David Farning
2007-10-24 17:11 ` Koen Kooi [this message]
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=471F7CC9.3060904@student.utwente.nl \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox