[doc] defining OpenEmbedded

[doc] defining OpenEmbedded

[David Farning]

Getting started is coming along nicely.

I am strugging with the way open embedded uses to terms.
local.conf
metadata

In the first case, the term local.conf implies a configuration file
that makes a program work correctly on a local machine.  OE uses the
file local.conf to define the top level build parameters for a bitbake
build.  That is pretty confusing.  It would be more clear if
local.conf was called build.conf.

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.

It seems like the term local.cconf and metadata may have outgrown
their original usage as OE became more advanced.

Thanks
David Farning

Re: [doc] defining OpenEmbedded

[Michael Krelin]

> 
> In the first case, the term local.conf implies a configuration file
> that makes a program work correctly on a local machine.  OE uses the
> file local.conf to define the top level build parameters for a bitbake
> build.  That is pretty confusing.  It would be more clear if
> local.conf was called build.conf.
> 

The whole OE is about *building* stuff, so calling it 'build.conf' is 
redundant, while 'local.conf' is quite explanatory because it contains 
the data local to this particular build.

> 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.

Well, the "data" are packages themselves, so
OE actually contains metadata, that is the information on where to 
retrieve the data from and how to handle it to produce code. I'm not 
sure if it's the perfect term, though, but is there real need to change it?

Love,
H

Re: [doc] defining OpenEmbedded

[Marcin Juszkiewicz]

Dnia środa, 24 października 2007, David Farning napisał:

> In the first case, the term local.conf implies a configuration file
> that makes a program work correctly on a local machine.  OE uses the
> file local.conf to define the top level build parameters for a bitbake
> build.  That is pretty confusing.  It would be more clear if
> local.conf was called build.conf.

But there are auto.conf, local.conf and site.conf which define 
configuration for build. Common use is that site.conf contain 
informations like DL_DIR, preferred mirrors for GNU/SourceForge/Debian, 
amount of make and BitBake threads, local.conf contain informations 
related to build (DISTRO and some addons like rm_work, tinderbox) and 
auto.conf contain only MACHINE setting (so it can be regenerated from 
shell).

> 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.

OE is not task lists - it defines them but also define many other things. 
Ruleset sounds for me like other name of 'task list'.

-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

    I used to think the brain is the most wonderfull organ in my body, 
    till I realised what was telling me that

Re: [doc] defining OpenEmbedded

[Cliff Brake]

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

Re: [doc] defining OpenEmbedded

[David Farning]

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.

But, using the defination at
http://en.wikipedia.org/wiki/Metadata
does not seems to apply.

Metadata is data is data which describes the data. ie
<zipcode>54494</zipcode>
<telephonenumber>123-1234</telephonenumber>

A recipe on the other hand define what ingredients to use.  Source
files, patches, configs.... Then states what tasks to perform on the
ingredients to create the desired result.  Binaries compiled for an arch,
added to a filesystem, bundled in an image.

Patches contain the changes necessary to make a general package work on a
particular device.

Classes are a more abstract form of recipe.

Machine.conf and Distro.conf provide a high level abstraction for the
developer to define what classes and recipes to call to create a
distribution with the desired characteristics.

Am I missing anything in this very high level description?

Thanks
David Farning

Re: [doc] defining OpenEmbedded

[Koen Kooi]

-----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-----