Aarch64 package moderation policy
Hello! I recently learned that the AUR seems to have an actively enforced moderation policy preventing packages that either only work on aarch64, or are otherwise heavily focused/only useful on that platform. RFC0032 hasn't finalized yet, and of course it could still end up being rejected or otherwise put on indefinite hiatus... My outsider perspective is that it likely will happen though, so I'm working under that assumption. In this case, it's only a matter of time before non-x86 communities are accumulating around Arch upstream proper. RFC0032 already notes that: - Ideally, the AUR web interface / API is extended to allow filtering packages by architecture. I have a concrete proposal here. Let's say I (or someone else) were to contribute the necessary changes to aurweb, such that it exposed architecture info in the RPC (archlinux/aurweb#485), as well as adding support for filtering by architecture when searching. If this happened, and the search box on the AUR homepage defaulted to x86, would it be possible to relax the current moderation policy that restricts aarch64-only packages from living in the AUR? -Sam
Re: Aarch64 package moderation policy
Ey, 1. Not sure what RFC0032 is. All I see is "Some Thoughts on SRI's Proposed Real Time Clock, February 1970". 2. The AUR already has filtering by architecture. It seems like AUR folk just don't want to moderate ARM packages. -- Cheers, Aᴀʀᴏɴ OpenPGP_0x4E85967FC7C436BE.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Re: Aarch64 package moderation policy
Okay, I've just realized that Arch also has RfCs. Where can I view in-draft RfCs? -- Cheers, Aᴀʀᴏɴ OpenPGP_0x4E85967FC7C436BE.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Re: Aarch64 package moderation policy
Am 14.04.24 um 21:34 schrieb Aaron Liu: Okay, I've just realized that Arch also has RfCs. Where can I view in-draft RfCs? There is a respective repository: https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests
Re: Aarch64 package moderation policy
Yarr, matey! On Sunday, 14 April 2024 at 9:33 PM, Aaron Liu wrote: > 1. Not sure what RFC0032 is. All I see is "Some Thoughts on SRI's > Proposed Real Time Clock, February 1970". I'm referring to this: https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/32 > 2. The AUR already has filtering by architecture... Eh? Where are you seeing architecture filtering in the AUR? Maybe I'm a*especially* dense tonight, but I can't see anything like that. Are you thinking of the architecture filtering available @ archlinux.org/packages perhaps? -Sam
Re: Aarch64 package moderation policy
Ahoy! Yeah, it seems I got confused over the two interfaces. Sorry about that, I'm the dense one. -- Cheers, Aᴀʀᴏɴ OpenPGP_0x4E85967FC7C436BE.asc Description: OpenPGP public key OpenPGP_signature.asc Description: OpenPGP digital signature
Re: Aarch64 package moderation policy
On Sun, 14 Apr 2024 18:02:08 + Sam Day said: > Hello! > > I recently learned that the AUR seems to have an actively enforced moderation > policy preventing packages that either only work on aarch64, or are otherwise > heavily focused/only useful on that platform. > > RFC0032 hasn't finalized yet, and of course it could still end up being > rejected or otherwise put on indefinite hiatus... My outsider perspective is > that it likely will happen though, so I'm working under that assumption. > > In this case, it's only a matter of time before non-x86 communities are > accumulating around Arch upstream proper. RFC0032 already notes that: > > - Ideally, the AUR web interface / API is extended to allow filtering > packages by architecture. > > I have a concrete proposal here. Let's say I (or someone else) were to > contribute the necessary changes to aurweb, such that it exposed architecture > info in the RPC (archlinux/aurweb#485), as well as adding support for > filtering by architecture when searching. If this happened, and the search > box on the AUR homepage defaulted to x86, would it be possible to relax the > current moderation policy that restricts aarch64-only packages from living in > the AUR? -Sam I'd +1 this. I actually have some magic in my PKGBUILDS to deal with low memory systems and that was actually a bi-product of building pkgs on a rpi3 with only 1G RAM (though it could apply to x86 too). The package is portable to any arch that's sane (all the major ones still left)so it's not aarch64 only, but in principle I think this RFC is a good thing. Aarch64 "desktop/laptop" class CPUs other than the m1/2/3 are well on their way (well some say already here - I use one as a daily driver at work, a 32 core Ampere). The time will be coming when alarm (a separate project though IMHO a close cousin) may even start pumping out bootable ISO images (some people have been doing this before on their own). It'd not make sense to make a bigger wedge between close relatives. -- - Codito, ergo sum - "I code, therefore I am" -- Carsten Haitzler - ras...@rasterman.com
Re: Aarch64 package moderation policy
On 14/04/2024 19:02, Sam Day wrote: Hello! Hi Sam, [..] Let's say I (or someone else) were to contribute the necessary changes to aurweb, such that it exposed architecture info in the RPC (archlinux/aurweb#485), as well as adding support for filtering by architecture when searching. We welcome contributions to our projects - please join #archlinux-aurweb to collaborate and proceed from here :) Cheers, -- Leonidas Spyropoulos Developer & DevOps PGP: 59E43E106B247368 244740D17C7FD0EC
