ChanServ changed the topic of #asahi-alt to: Asahi Linux: porting Linux to Apple Silicon macs | User-contributed/unofficial distribution ports | Logs: https://alx.sh/l/asahi-alt
mikelee has quit [Remote host closed the connection]
mikelee has joined #asahi-alt
ellyq has quit [Quit: system poweroff requested]
mikelee has quit [Ping timeout: 480 seconds]
cylm has joined #asahi-alt
cylm_ has quit [Ping timeout: 480 seconds]
possiblemeatball has quit [Quit: Quit]
sefidel has quit [Remote host closed the connection]
sefidel has joined #asahi-alt
mikelee has joined #asahi-alt
cylm has quit [Ping timeout: 480 seconds]
mikelee has quit [Ping timeout: 480 seconds]
mikelee has joined #asahi-alt
mikelee has quit [Ping timeout: 480 seconds]
<mps>
cy8aer: aren't there post install/upgrade trigger in debian to run script/program when package is installed upgraded (moved discussion here from #asahi-dev)
lena has joined #asahi-alt
<cy8aer>
Yes there must be (for e. g. generating grub-update). But I do not know where and I just search them. So for all with debian knowledge: where is the post-install hook for kernels? I hope not in the package itself...
<cy8aer>
mps: Yes there are in package pre/post-install scripts. But I hope that these are also trigger something outside of the kernel package. If you put the m1n1-update-process in the in package post-install you have some impacts for the generic package (I am thinking about the future with a vanilla debian kernel and the asahi stuff included)
<cy8aer>
If you put it inside the package the kernel must depend on m1n1, u-boot, and the asahi-scripts for all. And that I try to avoid that.
<cy8aer>
s/trigger/triggering/g
<mps>
yes, for now this is not easy to integrate into distros with mainline kernel
<mps>
maybe it is easy but I have no idea how
<mps>
maybe pre/post scripts should be more 'smart', i.e. examine hardware on which it runs
<cy8aer>
I am just working on it as a little project and there will be a in kernel post-install of course.