On 31-07-2023 06:26, Chih-Hsuan Yen wrote:
Thank you for bringing this up. Current guidelines for packages using prebuilt binaries, which are added in 2019 [1], are indeed unclear about Java packages. Literally, there is no rule about whether such Java packages should use a package name with "-bin" suffix or not. I propose to require the "-bin" suffix for new Java package using prebuilt binaries while allow existing packages without the "-bin" suffix (i.e., no need to submit deletion/merge requests for them).
A modified rule can be:
* Packages that use '''prebuilt''' [[wikipedia:Deliverable|deliverables]], when the sources are available, must use the {{ic|-bin}} suffix. An exception to this is with [[Java package guidelines#Java packaging on Arch Linux|Java]], where new Java packages using prebuilt binaries must use the {{ic|-bin}} suffix, while existing such packages without the {{ic|-bin}} suffix are allowed. The AUR should not contain the binary tarball created by makepkg, nor should it contain the filelist.
Any opinions?
[1] https://wiki.archlinux.org/index.php?diff=572792
Best,
Chih-Hsuan Yen (yan12125)
A few comments : - package guidelines in archwiki are valid for the whole archlinux community, not just aur. aur-general is not the right place to discuss them. (no idea if an RFC , wiki talk page , arch-general , arch-dev-public etc are the right place is) . - java has the concept of JAR files , https://en.wikipedia.org/wiki/JAR_(file_format) Technically using jar files is not 'building from source ' but they are not machine executable and not considered binaries . Currently such packages don't get a -bin suffix, are you proposing new packages using jar files will require a -bin suffix ? Lone_Wolf