<beerman>
I will be knocking on a few other "crucial" ports from my pov, pipewire+pulseaudio (and wireplumber), sway and friends.
<beerman>
building in the container with the script isn't too bad 😄 the second pi helps though, too bad I don't have a third
<pitillo>
never heard about Asahi, I'll try to take a look, sounds promising
<pitillo>
perfect beerman
<beerman>
trying gcc-fotran right now
<mnkydeth>
I know I'm not really helping in any way. But would pkg-get be preferable to prt-get for the pi's? The only time prt-get would be used is when you need more/less stuff built into something then what is there by default?
<mnkydeth>
I am thinking pkg-get would be extremely beneficial for these types of devices.
<beerman>
sure, but who fuels the packages for you to download? not me.
<beerman>
also: why use a source based distro if you don't want to build your own packages?
<mnkydeth>
Very understandable. From a cost perspective the hosting a server for bandwidth could be an issue. The source based distro aspect ... We are all here for one reason or another I am sure. :) I was just thinking the pre-built packages for these devices that take extremely long peroids of time to compile would help people get up and running in a spot they need/want without taking weeks/months. The source
<mnkydeth>
aspect is still there, if you want different functionality in say firefox, or you don't need all the codecs for handbrake or asunder.
<jaeger>
If you want to save time compiling the same thing for multiple similar systems, sure, it would help
<mnkydeth>
I havn't setup a pkg-get repo on my server yet. However I store all the source and packages on my server now via nfs to save download time etc. Storing the pre-made packages for different archs I was thinking to myself I could get back up and running fast during re-installs if needed. I just havn't got that far yet with my setup. But This is more of a personal thing. The pi's ... I'm thinking a nice
<mnkydeth>
distcc setup might be in order once 3.7 is ready.
<beerman>
its a) cost but also b) effort
<jaeger>
Sure, should be pretty easy to use that setup
<beerman>
its where i draw the line, as i already generate enough cost and keep myself busy enough
<beerman>
if automation efforts done here with the github ci take off like discussed, this would be nice to use/have.