Closed hnez closed 1 year ago
We will most likely ship new default userconfig.yaml
s then and now with added features etc..
Users that do incremental updates from release to release via rauc install
may however never see those.
Should we add a special case to our rauc hook.sh to create a userconfig.yaml.default
or something like that with the file shipped by the bundle?
We will most likely ship new default
userconfig.yaml
s then and now with added features etc.. Users that do incremental updates from release to release viarauc install
may however never see those. Should we add a special case to our rauc hook.sh to create auserconfig.yaml.default
or something like that with the file shipped by the bundle?
How about deploying our file as userconfig.yaml
and userconfig.yaml.default
. But only migrate userconfig.yaml
. In this case we should probably add a comment to the file describing what file does what.
In case of a breaking change we must inform the user in the changelog, I guess.
How about deploying our file as
userconfig.yaml
anduserconfig.yaml.default
. But only migrateuserconfig.yaml
. In this case we should probably add a comment to the file describing what file does what.
I like that. See the implementation I've just pushed.
This should make it easier to attach USB hubs to the TAC and getting the matches right.
I'm not too experienced with jinja2 so I've had some trouble working around the scoping rules (
set
ing a variable in ainclude
d file does not have an effect on the file that did theinclude
ing, but modifing the variable in another way does). And preventing the output from myusb_ports.pop
and.extend
tricks from being rendered (that's what theand '' and
or ''` are for). Maybe you have some better idea.@a3f could this be of any use to you?