Hi,
Kevin is right, but it should be mentioned that it is specifically
disallowed to put release candidates into a stable package. Exceptions can be
read on the wiki [1].
Regards,
Vince
[1] https://wiki.archlinux.org/title/Arch_package_guidelines#Package_versioning
If 1.0.0-rc.3 is why they're flagging it out of date, perhaps you could
reply to them and explain why it's not out of date; an rc is a release
candidate, but not necessarily a true release. After rc makes its way to
a true release, that's when upstream is telling everybody that there's a
new releas
Hi,
I maintain the gnudatalanguage package on the aur. The current release is 0.9.9
(from 2019); however, there is 1.0.0-rc.3 available on their webpage.
I recall having read somewhere in the docs that pushing rc version is generally
discouraged on the aur, but got a out-of-date flagging today.
Hi guys,
same here, in my case it's Racer [1]. The start script is included as
source (I didn't supply a desktop file because I didn't find a suitable
icon). Also glad about constructive feedback!
All the best,
Michael
[1] https://aur.archlinux.org/packages/racer-cg/
Am Fr., 30. Juli 2021 um 17
Hi, Vincent.
I also contributed a wine-based application recently [1] and found the
examples at https://wiki.archlinux.org/title/Wine_package_guidelines
very helpful. Since the wine prefix typically needs to be at least
partially writable, I chose to place the read-only files under /usr/share
and
Hi Vince,
About number 2, you can include the files alongside the PKGBUILD in the git
repo you push to the AUR, then add them to your "sources" array. Then, in
package(), you can use the "install" or "cp" command to move the files to their
desired location in the package.
Welcome to the mailin
Hello,
This is my first time interacting with a mailing list, so please let me
know if I've done something wrong, or I'm asking in the wrong place.
I plan to submit a binary PKGBUILD for REXPaint, and since it's
distributed as a portable binary for WINE, I have a couple questions
about the guidel