Re: [OE-core] Yocto rpm packages do not keep the modified CONFFILES

2024-03-12 Thread Alexander Kanavin
On Tue, 12 Mar 2024 at 02:57, Chen, Qi 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

Re: [OE-core] Yocto rpm packages do not keep the modified CONFFILES

2024-03-11 Thread Chen Qi via lists.openembedded.org
@lists.openembedded.org Subject: Re: [OE-core] Yocto rpm packages do not keep the modified CONFFILES On Mon, 11 Mar 2024 at 11:09, Böszörményi Zoltán wrote: > Yes, I am aware. But why not use the package manager's own features > instead of adding a workaround? Because I see it the opposite way: nor

Re: [OE-core] Yocto rpm packages do not keep the modified CONFFILES

2024-03-11 Thread Alexander Kanavin
On Mon, 11 Mar 2024 at 11:09, Böszörményi Zoltán wrote: > Yes, I am aware. But why not use the package manager's > own features instead of adding a workaround? Because I see it the opposite way: noreplace in this case is a workaround for a file name conflict between what the tool generates and

Re: [OE-core] Yocto rpm packages do not keep the modified CONFFILES

2024-03-11 Thread Zoltan Boszormenyi
2024. 03. 11. 10:37 keltezéssel, Alexander Kanavin írta: On Mon, 11 Mar 2024 at 10:30, Böszörményi Zoltán 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

Re: [OE-core] Yocto rpm packages do not keep the modified CONFFILES

2024-03-11 Thread Alexander Kanavin
On Mon, 11 Mar 2024 at 10:30, Böszörményi Zoltán 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

Re: [OE-core] Yocto rpm packages do not keep the modified CONFFILES

2024-03-11 Thread Zoltan Boszormenyi
2024. 03. 09. 17:39 keltezéssel, Alexander Kanavin írta: I think (noreplace) flag only matters when the file has been manually edited after rpm installation and its checksum diverges from what is registered in rpm database. Which is not a common scenario in embedded. So from Yocto's POV it's

Re: [OE-core] Yocto rpm packages do not keep the modified CONFFILES (was: BB Equivalent for %config(noreplace))

2024-03-09 Thread Alexander Kanavin
I think (noreplace) flag only matters when the file has been manually edited after rpm installation and its checksum diverges from what is registered in rpm database. Which is not a common scenario in embedded. If you manually edit the file on target, you might as well manually resolve which

Re: [OE-core] Yocto rpm packages do not keep the modified CONFFILES (was: BB Equivalent for %config(noreplace))

2024-03-08 Thread Richard Purdie
On Fri, 2024-03-08 at 03:20 -0800, Zoltan Boszormenyi wrote: > Hi, > > I just found out that if an updated package ships a modified > configuration file, then the Yocto package upgrade does this: > > * rename the edited conffile to conffile.rpmsave > * install the new, modified one from the

[OE-core] Yocto rpm packages do not keep the modified CONFFILES (was: BB Equivalent for %config(noreplace))

2024-03-08 Thread Zoltan Boszormenyi
Hi, I just found out that if an updated package ships a modified configuration file, then the Yocto package upgrade does this: * rename the edited conffile to conffile.rpmsave * install the new, modified one from the package instead of: * keep the edited conffile intact * install the new,