Hey! Thanks for the reply. I looked into it a lot more and it looks extremely complex and difficult (to me at least). It's almost the same as building a distribution from the ground up from what I have gathered (?). Like, every package would have to be compiled for ARM, even packages that are already compiled for Arch Linux ARM? I did look into it but its a lot to take in. Is this correct? For example, apache2 is compiled and working on Arch Linux ARM but using that already compiled package in an ARM build of KaOS might not work or have weird issues because packages depend on libraries, and the library being used for apache2 on X version of Arch Linux ARM won't work on KaOS ARM (In theory) because its expecting a different library... Struggling a bit to understand this.
And for the cross-compilation toolchain, would it be possible to cross-compile for a Raspberry Pi but on an M1/M2 series CPU? It sounds like this might cause problems, but I don't really understand enough about this yet. Do I need an x86_64 PC for the toolchain to work properly?
I also have no idea about compiling packages and stuff like that. I think to have a chance to make an ARM version of KaOS I need to know more about how a Linux distribution is actually made, and how you keep track of it all... I know a little bit about version control (a very little bit) - Is stuff like that essential for making an ARM version of KaOS? How do you organise all the packages and stuff that go into making a distro like KaOS in the first place?
The more I look into this, the more questions I have haha
Edit: Also, I was looking at the KaOS Packages page: https://kaosx.us/packages/packages.php?sortby=name&sortdir=asc
Is this all the packages that make up KaOS? So I would need to compile 2352 packages to make an ARM compatible version of KaOS? (From the total packages number down the bottom of the KaOS Packages page)
BTW, do you guys have a discord channel for this distro? I had a look but can't seem to spot it. NM, found the Contact page. (There is no discord)