On Wednesday 11 June 2014 22:56:19 Saul Wold wrote: > This is a little further along, I would really like to get some > feedback on the direction I am taking this. > > The idea is that a block of anonymous code will generate all the > metadata and do_install() function for the existing config files > such that a .bbappend can be created to override specific files > from a single recipe instead of from 10-12 different .bbappends.
I have some reservations about this change as-is. I certainly accept that currently the placement of typical BSP config files is a bit of a mess, and new users definitely find it difficult to know where to go to change a particular file; however there will always be config files this recipe doesn't cover. Most significantly, it also requires everyone with existing BSP and distro layers to go and migrate their bbappends over to the new structure, for not that much gain. If we are going to go down this route, we absolutely must have a script which migrates existing bbappends to this new layout. We'll also need to ensure runtime upgrades work, i.e. PR values will have to increase from the old packages to the new ones provided by the single recipe. As a more general improvement in this area, I'd really like to see us have some tooling around finding where a particular config file (or other file I want to replace) comes from and then creating the bbappend to substitute my version. We have the part that tracks down the recipe from a file - albeit in a not-very-easy-to-use form - in scripts/oe-pkgdata-util (with its "find-path" command); Toaster has the functionality to do this as well. This solution has the benefit of being able to work for any configuration file (or other file) that any recipe in any layer introduces. In fact this will be of benefit even if we decide to go ahead with the conf-files move, so I've entered an enhancement request to cover it separately: https://bugzilla.yoctoproject.org/show_bug.cgi?id=6447 Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre -- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
