2024. 03. 11. 10:37 keltezéssel, Alexander Kanavin írta:
On Mon, 11 Mar 2024 at 10:30, Böszörményi Zoltán <zbos...@gmail.com> wrote:
If you manually edit the file on target, you might as well
manually resolve which version you want after the update as both are
available regardless of whether (noreplace) was used or not. Or
perhaps merge the manual edits into the new version.
The interesting use case here is that the configuration file
in question is generated on the machine using a GUI,
while a minimal stock version of the file is shipped by the package.
This can be handled by shipping the stock config under a different
file name (e.g. conf.sample or conf.template)?
Yes, I am aware. But why not use the package manager's
own features instead of adding a workaround?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196931):
https://lists.openembedded.org/g/openembedded-core/message/196931
Mute This Topic: https://lists.openembedded.org/mt/104859795/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
