groovy2shoes has quit [Read error: Connection reset by peer]
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Hey r0ni: what about adding them to their oficial overlays? At least opt/xorg ones. You can create PR to take advantage of those ports, and if you prefer, you can keep yourself as maintainer for them
SiFuh-AFK has quit [Remote host closed the connection]
SiFuh-AFK has joined #crux-devel
<r0ni>
pitillo: that is the plan once i've had a chance to go through xorg at least, before i look into contrib deeper. My time has been low this week for working on lists yet
<cruxbridge>
<pitillo (@pitillo:crux.nu)> That sounds great! We need to plan how to improve all that work to not create more dependency, as you are one of the most focused on ARM arch, like Tim
<cruxbridge>
<pitillo (@pitillo:crux.nu)> And obviously, there is no need to rush
<r0ni>
i've thought about this, and it's really a catch 22, but manually removing arch specific things from footprints is an idea, but maybe whatever pre-processes that stuff could/should do that
<r0ni>
python packages stand to benefit but also footprints would be less useful if more things were stripped from them
<pitillo>
yeah, putting hands on arch dependent footprints could be a big step ahead for maintaining ARM overlays. Most of them are currently related to arch specific footprints
<pitillo>
and specific --build overlays are being fixed upstream slowly. Some years ago there were a lot of ports which needed an specific --build for aarch64
<r0ni>
yeah it's very few needing --build nowadays