Thanks for pointing that out – I must've skipped that point when it came to mentioning JAVA.
Anyway: it's not clear to me what exactly is meant by that. The whole phrase is: "Packages that use prebuilt deliverables, when the sources are available, must use the -bin suffix. An exception to this is with Java. The AUR should not contain the binary tarball created by makepkg, nor should it contain the filelist."
From how I understand it, it's more about things like adding the pkg.tar. to the AUR (as in commiting it to the AUR), and not about using a pkg.tar. from elsewhere as a source. So as long as it's a -bin
package, everything should be alright.
Which would, to my mind, "make the most sense" – because why would this be any different than a binary packaged for anything else?; as long as I'm not pulling the pkg.tar. from the official upstream repos (or putting the pkg.tar. on the AUR which would fit better with the "should not contain the binary tarball.." part).
I might still be totally in the wrong here, but neither do I see what about my approach here is detrimental (except it being somewhat inelegant) to Arch / the AUR, nor am I certain it's meant the way you say.
So if you could help me out a bit further on that (by clarifying that it is indeed meant the way you say it is) or if you could provide me a somewhat more clearly phrased source / some statement somewhere, that would be great!
Again, not trying to be a pain here – just trying to see what's the best way to somehow get everyone happy on this ^^
Pinned Comments
lsf commented on 2021-11-10 12:14 (UTC) (edited on 2023-04-17 07:18 (UTC) by lsf)
https://wiki.archlinux.org/title/Arch_User_Repository#Acquire_a_PGP_public_key_if_needed
gpg --keyserver hkp://keyserver.ubuntu.com --search-keys 031F7104E932F7BD7416E7F6D2845E1305D6E801
/edit: starting with 112.0-1, the binaries are signed with the maintainers shared key, so
gpg --keyserver hkp://keyserver.ubuntu.com --search-keys 662E3CDD6FE329002D0CA5BB40339DD82B12EF16
should do the trick instead. I've also signed the key with the previously used key, so you have at least some guarantee that it's not a malicious attack :)