Spent a fair chunk of the day digging into .deb packaging. Got the thing to build, which to be fair was no small feat in itself, HOWEVER the resulting .debs had no useful files in it - ok that should be an easy fix right?
Great now I'm running into trying to convince the dh (debhelper) system actually install the python wheel that gets built into the right place and actually put those bits into the package - and for the life of me I cannot find a good example and/or docs on this. To say it's frustrating is a bit of an understatement.
To flip this on it's side: I've had RPMs for this particular thing done 3 months ago, and didn't take nearly as long to figure out what it was trying to do.
*sigh*
Do I know any deb maintainers I can ask stupid questions of?
🥳 My #kernel vanilla repositories for #Fedora #Linux[1] started shipping[2] kernels with #realtime aka #PREEMPT_RT support. 🥳
[1] https://fedoraproject.org/wiki/Kernel_Vanilla_Repositories
[2] 6.12-pre and later only obviously, as the latest stable series does not support it out-of-the-box
This is Matt (aka Mr #ASIC) who works to make chip design more accessible to students and enthusiasts. The Tiny Tapeout project: https://tinytapeout.com uses a fully open source pipeline to synthesise, verify and layout asic designs and combine them with other projects to amortise the wafer cost and make custom designs possible. #dvcon