[OE-core] want to confirm that include/require is a pure textual substitution

[Robert P. J. Day]

  currently writing a tutorial involving OE and working up to yocto
and want to verify a couple things.  i'm reading the OE manual,
section on include/require:

http://docs.openembedded.org/usermanual/usermanual.html#recipes_require

and want to verify that that is purely a textual inclusion, so that
*anything* that is common across a number of .bb files can be
centralized in a .inc file, correct?

  and on that note, a larger question about the OE manual itself.  in
that same section, there's a reference to the cherokee package, and
the alleged .bb file:

PR = "r7"

SRC_URI_append = "file://configure.patch \
                  file://Makefile.in.patch \
                  file://Makefile.cget.patch \
                  file://util.patch"

require cherokee.inc

do_configure() {
        gnu-configize
        oe_runconf
        sed -i 's:-L\$:-L${STAGING_LIBDIR} -L\$:' ${S}/*libtool
}

  unsurprisingly, that's out of date as the current .bb file is
simply:

require cherokee.inc

PR = "${INC_PR}.0"

SRC_URI[md5sum] = "21b01e7d45c0e82ecc0c4257a9c27feb"
SRC_URI[sha256sum] =
"042b5687b1a3db3ca818167548ce5d32c35e227c6640732dcb622a6f4a078b7d"

but that's not my point.  since i want my tutorial to walk someone
through various files, given the split into the oe-core and
meta-openembedded layers, i'm thinking of using examples strictly out
of oe-core since there's more than enough there.  but the cherokee
example is in the meta-openembedded layer, and that distinction
doesn't appear to be made early in the OE manual anywhere.

  is there a plan to revise that manual to incorporate the
distinction?  is there a newer manual elsewhere?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================