On Tue, 12 Mar 2024 at 02:57, Chen, Qi <qi.c...@windriver.com> wrote: > > Packages + overrides are a very common way to configure/customize images. > > Take OE itself as an example, the sshd_config is a conffile for openssh, but > in rootfs-postcommands.bbclass, it is customized. > This means sshd_config might be different from the one that is recorded in > rpm database. This is a similar situation with the original question. > The original question is basically equal to: are we going to keep the > sshd_config we customized when we upgrade the openssh on target? > > Ideally, packages should be designed to allow config snippets > (/etc/xxx.conf.d/) or some override mechanism (default conf in /usr/lib and > override in /etc). But there'll always be packages that lack such mechanisms. > Using 'noreplace' seems a reasonable choice. > > For the default behavior of OE, I'd suggest we change to use 'noreplace'. > Because the more unlikely people modify their target files (as Alex pointed > out for embedded devices), the more important those modifications might be.
With this I agree. There's also just been a patchset that refactors ssh config into just that kind of snippet mechanism. But if we add noreplace, we also need to ensure its behaviour is consistent with deb and ipk backends as RP said. Alex
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#196981): https://lists.openembedded.org/g/openembedded-core/message/196981 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] -=-=-=-=-=-=-=-=-=-=-=-
