On 04/19/2017 04:03 PM, David Vincent wrote:
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 ?
By all means please do so. Yocto lacks a solution for configuration
management, and this was discussed some time ago, although I cannot
anymore find where it happened. Mark, do you remember?
Alex
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
