<beerman>
I am not sure if it should be kept in that repo or not
<beerman>
maybe the Makefile can be tweaked to not build and include it or so too, not sure, just thinking out loud here
<pitillo>
yeah beerman, that's the right repo but the crux-arm-release builder needs some love to avoid non-core overlayed ports
<r0ni>
hrm they do have a bin kernel repo as well, but i'm also not sure what kind of support mainline has for rpi kernels either, it's not running on rpi without it tho so...
<r0ni>
kernels=devices
<r0ni>
but yeah if building an opt rootfs, maybe some way to skip that port or some other solution?
<beerman>
yeah maybe just adding some logic will suffice, okay
<r0ni>
I'd always build a standard one and change the opts for said device
<beerman>
don't get me wrong, good idea to add a default kernel because it is a bit different than your normal kernel procedure :)
<beerman>
i just noticed it during a optimized test build with the Makefile
<r0ni>
speaking of, that port could use an update, maybe later I can, its bed time now heh
<beerman>
Sure, hit me up for the key later :)
stratofall has quit [Quit: leaving]
crux-arm-bot has joined #crux-arm
<crux-arm-bot>
[ crux-ports-opt-arm ]: talloc: update to 2.4.3
crux-arm-bot has left #crux-arm [#crux-arm]
crux-arm-bot has joined #crux-arm
<crux-arm-bot>
[ crux-ports-opt-arm64 ] [3.7] talloc: update to 2.4.3