On mercredi 19 avril 2017 13:57:40 CEST Alexander Kanavin wrote: > On 04/19/2017 02:53 PM, David Vincent wrote: > >> This kind of thing is better done via ROOTFS_POSTPROCESS_COMMAND, I > >> think. Look for examples in rootfs-postcommands.bbclass. > > > > The problem of ROOTFS_POSTPROCESS_COMMAND is that it is a one shot > > function > > that is run at image creation. In my case, I must be able to upgrade the > > package over time via package management tools. Sorry for not bringing > > that up before. > > What is it in the openssl config file that must be managed via package > updates? The problem is that I must be able to manage the configuration of a machine without physical intervention and only via package upgrades. A new configuration can be applied simply by incrementing the PR of a configuration package.
But maybe this is a use case only needed by me and I should manage it in my own specific layer ? Now that I think of it, I have the same kind of problem for all machine specific configurations. For now, I just replace the PACKAGE_ARCH in my BSP layer with a machine specific one to indicate that a package contains a configuration valid only for a specific machine. Maybe, in a future release, it should be desirable to create -conf packages based on the CONFFILES variable ? I don't know if it's a good idea, but maybe I could bring that up on the architecture mailing list ? > > Alex David -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
