Hi Paul, > > I verified this by building an image - the sysctl.conf that ends up in > > the final image is the one from meta-bsp, not the one from meta-custom. > > But if I switch the name of base-files_%.bbappend in meta-custom to > > base-files_3.0.14.bbappend, this is what I get: > > > # $FILESEXTRAPATHS [5 operations] > > > # set poky/meta/conf/documentation.conf:172 > > > # [doc] "Extends the search path the OpenEmbedded build > system > > > uses when looking for files and patches as it processes recipes > and > > > append files." # _prepend > > > meta-bsp/recipes-core/base-files/base-files_3.0.14.bbappend:3 # > > > "meta-bsp/recipes-core/base-files/base-files:" > > > # _prepend > > > meta-custom/recipes-core/base-files/base-files_3.0.14.bbappend:6 > # > > > "meta-custom/recipes-core/base-files/base-files:" > > > # set data_smart.py:432 [finalize] > > > # "meta-bsp/recipes-core/base-files/base-files:" > > > # set data_smart.py:432 [finalize] > > > # > > > "meta-custom/recipes-core/base-files/base-files:meta-bsp/recipes- > cor > > > e/base-files/base-files:" # computed: > > > # > > > "meta-custom/recipes-core/base-files/base-files:meta-bsp/recipes- > cor > > > e/base-files/base-files:" > > > FILESEXTRAPATHS="meta-custom/recipes-core/base-files/base- > files:meta > > > -bsp/recipes-core/base-files/base-files:"> > > > And now the sysctl.conf file is being pulled from meta-custom. > > That absolutely should not happen. If you change it back does it revert to > the version from meta-bsp? The wildcarding should not change the order in > which the files are applied. The only corner case I can think of would be > if the layer priority values are the same number - this isn't the case is > it?
The behavior does reappear if I change the file name back to a wildcard. And no, the layers are different priorities - meta-custom is priority 8 and meta-bsp is priority 6. Definitely sounds like there's some unexpected behavior here. I am going to dig in some more and see if I can find a limited test case that reproduces the issue, and then I'll get a bug report opened. Thanks! Nick -- _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
