And more I wish to upload the main stream especially about the 'base/base-devel' packages.
For now, I think you should use Arch Linux ARM http://archlinuxarm.org/
]]>I'm not agree it. In most case, the same name package has already exist there, and the owner may not with to merge different arch, because they don't have such machine to test it. And more I wish to upload the main stream especially about the 'base/base-devel' packages.
]]>All the best,
-HG
]]>Maybe Arch will support more architectures in the future, but there are very few that are likely to be considered for addition I think (namely ARM).
All the best,
-HG
]]>I've modified many build script in sh4 CPU.
But I guess maybe Arch Linux don't welcome added these modification.
I've two idea about to let Arch Linux PKGBUILD more useful.
Method 1: let makepkg support PKGBUILD.<arch>
For those only 'arch' line different PKGBUILD, we don't allow people to upload to arch source.
For those specific CPU (eg. armv5, armv7, sh4, ...), we can upload PKGBUILD.<arch> and <name>-<issue>.patch.<arch>
If the makepkg found there exist newer PKGBUILD, it show 'Warn: version different to PKGBUILD", and still use PKGBUILD.<arch> to build.
Method 2: only keep one PKGBUILD and accept modification in specific situation.
For those only 'arch' line different PKGBUILD, we don't allow people to upload the patch.