Are those android-$arch-$package packages allowed in AUR?
Hello, With reference to [1], are those android-$arch-$package packages allowed in AUR? [2]
Packages in the AUR should be useful on Arch Linux, which is currently an x86_64-only distribution.
It seems that those packages are for Android (not useful on Arch), which may not meet the above requirement. Best regards, gnlrdrvo [1] https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/me... [2] For examples, please refer to the packages listed in "Required by" section: https://aur.archlinux.org/packages/android-configure?all_reqs=1#pkgreqs
there is also big bunch of `*-mingw` (ie windows-only) packages in AUR, but for some reason i saw the AUR moderators hunting only for non-x86-64, but completely ignoring those - so indeed i think some formal clarifications would be useful On Tue, Jan 14, 2025 at 9:42 AM <digear466@mailgw.com> wrote:
Hello,
With reference to [1], are those android-$arch-$package packages allowed in AUR? [2]
Packages in the AUR should be useful on Arch Linux, which is currently an x86_64-only distribution.
It seems that those packages are for Android (not useful on Arch), which may not meet the above requirement.
Best regards, gnlrdrvo
[1]
https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/me... [2] For examples, please refer to the packages listed in "Required by" section: https://aur.archlinux.org/packages/android-configure?all_reqs=1#pkgreqs
On 14-01-2025 09:59, Actionless Loveless wrote:
there is also big bunch of `*-mingw` (ie windows-only) packages in AUR, but for some reason i saw the AUR moderators hunting only for non-x86-64, but completely ignoring those - so indeed i think some formal clarifications would be useful
The mingw packages are used by people that want to windows programs on a linux system (cross-compiling) . See https://wiki.archlinux.org/title/Cross-compiling_tools_package_guidelines and https://wiki.archlinux.org/title/MinGW_package_guidelines for info on how they work.
Just so you know on the official repo On 2025-01-14 02:59 AM, Actionless Loveless wrote:
there is also big bunch of `*-mingw` (ie windows-only) packages in AUR, but for some reason i saw the AUR moderators hunting only for non-x86-64, but completely ignoring those - so indeed i think some formal clarifications would be useful
Just so you know on the official repo there are several mingw packages. On AUR, in order to build wine-wow64 (if using this one from AUR you don't need any multilib package) you need those mingw packages, in particular for wine-wow64. So be careful when removing mingw stuff. BTW, I don't agree with the adopted enforcing, but as it is, care must be taken when removing packages... Look at the makedepends for wine-wow64:
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=wine-wow64#n50
which actually installs:
% pacman -Qs mingw local/mingw-w64-binutils 2.43-1 (mingw-w64-toolchain mingw-w64) Cross binutils for the MinGW-w64 cross-compiler local/mingw-w64-crt 12.0.0-1 (mingw-w64-toolchain mingw-w64) MinGW-w64 CRT for Windows local/mingw-w64-gcc 14.2.0-3 (mingw-w64-toolchain mingw-w64) Cross GCC for the MinGW-w64 cross-compiler local/mingw-w64-headers 12.0.0-1 (mingw-w64-toolchain mingw-w64) MinGW-w64 headers for Windows local/mingw-w64-winpthreads 12.0.0-1 (mingw-w64-toolchain mingw-w64) MinGW-w64 winpthreads library
And as mentioned, they are part of the official repos, but I guess there are counterparts on AUR, or complimentary mingw packages as well. Just so you know. -- Javier
On AUR, in order to build wine-wow64 (if using this one from AUR you don't need any multilib package) you need those mingw packages, in particular for wine-wow64.
There are 770 (!) mingw packages on AUR, I strongly doubt they all are dependencies for building wine. So I think either adjustment to the rules, or a big cleanup needs to be done.
On 14-01-2025 09:42, digear466@mailgw.com wrote:
Hello,
With reference to [1], are those android-$arch-$package packages allowed in AUR? [2]
Packages in the AUR should be useful on Arch Linux, which is currently an x86_64-only distribution.
It seems that those packages are for Android (not useful on Arch), which may not meet the above requirement.
Best regards, gnlrdrvo
[1] https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/me... [2] For examples, please refer to the packages listed in "Required by" section: https://aur.archlinux.org/packages/android-configure?all_reqs=1#pkgreqs
Jt seems my previous reply[1] was not seen, so I added all posters in this thread in the to-list of this message. A substantial amount of arch users build programs for other architectures on their archlinux systems . This is called cross compiling . https://wiki.archlinux.org/title/Cross-compiling_tools_package_guidelines shows how to setup an archlinux system to do that. The mingw packages are used to build windows programs on archlinux systems . I looked at a few of the android-* packages and they appear to have a similar purpose. TL;DR : the mingw and android packages are useful on an archlinux system and acceptable for AUR. Lone_Wolf [1] https://lists.archlinux.org/archives/list/aur-general@lists.archlinux.org/me...
A substantial amount of arch users build programs for other architectures on their archlinux systems .
in that case i think the upload rules should mention such exception for packages needed for [potential] cross-compilation as an exception. because currently it's not clear at all from just reading them
Hi
With reference to [1], are those android-$arch-$package packages allowed in AUR? [2]
Packages in the AUR should be useful on Arch Linux, which is currently an x86_64-only distribution.
It seems that those packages are for Android (not useful on Arch), which may not meet the above requirement.
What packages are you referring to exactly? Many android packages are runtime for the Android emulator run in Arch Linux, not for Android. They are the systems the emulator will run. Best regards -- Muflone
Hi Muflone,
For examples, please refer to the packages listed in "Required by" section: https://aur.archlinux.org/packages/android-configure?all_reqs=1#pkgreqs
e.g. android-aarch64-a52dec (make) android-aarch64-alsa-lib (make) android-aarch64-cdparanoia (make) android-aarch64-cppunit (make) android-aarch64-curl (make) android-aarch64-faac (make) android-aarch64-ffmpeg (make) ... ...
Many android packages are runtime for the Android emulator run in Arch Linux, not for Android. They are the systems the emulator will run.
Are there any Android emulator packages which require android-$arch-$package as build / runtime dependencies in their PKGBUILD? When I checked `android-emulator`, [1] it does not list any android-$arch-$package. gnlrdrvo [1] https://aur.archlinux.org/packages/android-emulator
Jan 15, 2025 23:10:51 digear466@mailgw.com:
Hi Muflone,
For examples, please refer to the packages listed in "Required by" section: https://aur.archlinux.org/packages/android-configure?all_reqs=1#pkgreqs
e.g.
android-aarch64-a52dec (make) android-aarch64-alsa-lib (make) android-aarch64-cdparanoia (make) android-aarch64-cppunit (make) android-aarch64-curl (make) android-aarch64-faac (make) android-aarch64-ffmpeg (make) ... ...
Many android packages are runtime for the Android emulator run in Arch Linux, not for Android. They are the systems the emulator will run.
Are there any Android emulator packages which require android-$arch-$package as build / runtime dependencies in their PKGBUILD? When I checked `android-emulator`, [1] it does not list any android-$arch-$package.
gnlrdrvo
Not muflone but from a quick look at the android-configure package which is a build dependency for all of them and the 2 dependencies of android-configure, it appears to me that these packages are intended for cross-compilation towards android rather than emulating. Besides, the purpose of emulating isn't to add packages to the host but rather to run them in the emulator, so regular android apk's would suffice for that. Cross-compiling however does require you to have the dependencies of a different operating system and/or architecture for which you are cross-compiling installed. Kusoneko
On Thu, 2025-01-16 at 01:26 -0500, Kusoneko wrote:
Not muflone but from a quick look at the android-configure package which is a build dependency for all of them and the 2 dependencies of android-configure, it appears to me that these packages are intended for cross-compilation towards android rather than emulating. Besides, the purpose of emulating isn't to add packages to the host but rather to run them in the emulator, so regular android apk's would suffice for that. Cross-compiling however does require you to have the dependencies of a different operating system and/or architecture for which you are cross-compiling installed.
Kusoneko
They are indeed for cross-compilation, I have used them in the past. I see no reason to remove them other than them being broken. Same for the mingw stuff. Cheers, Filipe Laíns
Should we update the ArchWiki page [1] then? e.g. Old:
The AUR and official repositories are intended for packages which install general software and software-related content, including one or more of the following: executable(s); configuration file(s); online or offline documentation for specific software or the Arch Linux distribution as a whole; media intended to be used directly by software.
New:
The AUR and official repositories are intended for packages which install general software and software-related content, including one or more of the following: executable(s); configuration file(s); online or offline documentation for specific software or the Arch Linux distribution as a whole; media intended to be used directly by software; cross-compilation towards another OS on `x86_64` or other architectures.
gnlrdrvo [1] https://wiki.archlinux.org/title/AUR_submission_guidelines#Rules_of_submissi...
On 18.01.25 at 1:48 (UTC+0000), digear466@mailgw.com wrote:
Should we update the ArchWiki page [1] then?
There is no need, the current wording does not exclude cross-compilation packages from being "legally" placed in the AUR. They fall under "general software", the list of examples on the wiki is not meant to be exhaustive. Cheers, Jakub
participants (8)
-
Actionless Loveless
-
digear466＠mailgw.com
-
Filipe Laíns
-
Jakub Klinkovský
-
Javier
-
Kusoneko
-
Lone_Wolf
-
Muflone