You are not logged in.
Pages: 1
There's an old thread here on the topic but I don't want to necrobump.
I maintain the package https://aur.archlinux.org/packages/openrsc-launcher-bin/ but want to drop the -bin suffix. There is no open-rsc-launcher package.
Is the proper action in this case to hit "Submit Request" and merge into the non-existant "open-rsc-launcher"?
Any guidance appreciated -
Offline
There is no open-rsc-launcher package.
That PKGBUILD there simply downloads an already-built .jar file (instead of building things from source), so that qualifies as a -bin package. Whether or not there is a non-bin package doesn't matter here AFAIK.
For the general case, you could push the package under the new name, and then request the old packagebase to be merged.
But again, this wouldn't be valid here.
Offline
That PKGBUILD there simply downloads an already-built .jar file (instead of building things from source), so that qualifies as a -bin package. Whether or not there is a non-bin package doesn't matter here AFAIK.
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.
Offline
Offline
Pages: 1