|
|
|
|
|
|
by em3rgent0rdr
2725 days ago
|
|
|
> "Arch Linux supports only x86_64. Void supports i686, x86_64, armv6, armv7 and aarch64..." Well Arch Linux Arm has optimized packages for soft-float ARMv5te, hard-float ARMv6 and ARMv7, and ARMv8 AArch64 instruction sets [1], which is even more. Arch main project used to support i686, but after removing official support, i686 is still carried on by Arch Linux 32. [2] Does it really matter if it is not under the same project? [1] https://archlinuxarm.org/
[2] https://archlinux32.org/ |
|
|
Right, Void does not provide pre-built packages for armv5, there are a few other architectures void works with but doesn't provide pre-build packages. this includes armv5, different mips targets and there are currently contributors working on getting powerpc and powerpc64 merged. powerpc64 will most likely become another architecture with pre-build packages.
> Does it really matter if it is not under the same project?
Yes, different projects apply different patches, have potentially different packages or provide different package versions.
With Void every package has the same patches applied, maintainers are "forced" to write portable patches that can be easily upstreamed. Package versions are usually the same (some exceptions), no delay.
I bet its easier for void to maintain all architectures at once than the man power required to maintain separate repositories and patches for the arch "forks".
Then you have the review overhead with forks, on void maintainers review commits to one repository, with the arch forks you have a fraction of the arch maintainers review commits to forks, while all others only review commits to the main repository.
Void makes it easier to maintain packages for different architectures, it provides xbps-src which cross compile to different architectures, it uses Travis-CI to build each pull request for different architectures.