Hi, Quoting Vagrant Cascadian (2023-10-12 06:09:11) > On 2023-10-11, Johannes Schauer Marin Rodrigues wrote: > > installing u-boot-menu does not create /boot/extlinux/extlinux.conf. Is > > there a reason for that? It gets triggered as expected when kernels get > > installed or upgraded but the postinst does not contain a codepath that > > gets triggered just on installation. So right now, after installing > > u-boot-menu I have to manually run u-boot-update. I shouldn't have to do > > that, right? > > I agree that it seems reasonable to expect it to run on package installation > or upgrade, sure! > > It would be nice to avoid running it multiple times in a single apt run, e.g. > upgrading the kernel and/or initramfs-tools and u-boot-menu at the same > time... but it also is not hugely resource intensive to occasionally run it > multiple times if that is too complicated to implement. That might end up > causing any backup files to get obliterated, though.
can we agree that resource usage is absolutely negligible for u-boot-update? You know how slow the imx8mq of my Reform is and even on that platform u-boot-menu takes 0.27 seconds to run (first run, cold cache -- subsequent runs are ~0.08 s faster). This leaves the problem of overwriting backup files. How about, for a start, let postinst run u-boot-update if /boot/extlinux/extlinux.conf.bak does not exist? This would cover the case of fresh installations and it would not overwrite anything because nothing existed before. Thanks! cheers, josch
signature.asc
Description: signature
