[oe] [doc] defining OpenEmbedded
hacker at klever.net
Wed Oct 24 12:47:24 CEST 2007
> 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?
More information about the Openembedded-devel