I’d be very careful with doing that. Imagine installation is aborted either via hardware failure or because the user pressed ctrl+c at the wrong time. Then you might have an updated extlinux.conf but the kernel isn’t working yet. Also, how do you handle the version? What do you do when there are multiple kernels installed at the same time? All of this can be solved by extlinux.conf being generated dynamically after kernel installation is complete and then being replaced atomically. In Debian, the package u-boot-menu does that job in case you want to have a look.
No. There are classic Reforms with imx8mq that do not support it but none of the newer models.
I should have been more clear. What I really meant was should I skip generating boot.scr entirely in exchange for generating extlinux.conf and it seems like yes. I’ll definitely generate it dynamically
I am going to try and make this a proper void package, but I don’t understand how debian packages work. Is there an easy way for me to see what commands are being run to build this package? I mostly just need to know what files get installed where
The magic for dkms packages in not in the build process. The “binary” package only contains source code. The real magic happens on the user’s computer when that source code is then compiled into a module at installation time.