[OE-core] appears to be inconsistency re: base-files between oe-core and meta-angstrom

[Robert P. J. Day]

  trying to build a "hardware-bringup-image" defined in angstrom layer
and running into:

ERROR: QA Issue: Fixup Perms: Unable to correct directory link, target already exists: /var/log -> /var/volatile/log
ERROR: QA Issue: Fixup Perms: Unable to correct directory link, target already exists: /var/run -> /run
ERROR: QA Issue: Fixup Perms: Unable to correct directory link, target already exists: /var/tmp -> /var/volatile/tmp

this would *appear* to be because oe-core defines, in
base-files_3.0.14.bb:

volatiles = "log tmp"
... snip ...
        for d in ${volatiles}; do
                ln -sf volatile/$d ${D}${localstatedir}/$d
        done
        ln -snf ../run ${D}${localstatedir}/run
        ln -snf ../run/lock ${D}${localstatedir}/lock

which seems to want to create /var/{run,log,tmp} as symlinks, but over
in meta-angstrom, we have base-files_3.0.14.bbappend which seems to
want to create them as actual directories instead:

dirs755 += "${localstatedir}/cache \
            ${localstatedir}/run \
            ${localstatedir}/log \
            ${localstatedir}/lock \
            ${localstatedir}/lock/subsys \
            ${localstatedir}/tmp \
            ${localstatedir}/volatile/tmp \
            /run \
           "

or am i misreading something?

rday

-- 

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

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