Package Details: golfscript 0.0.0-2

Git Clone URL: https://aur.archlinux.org/golfscript.git (read-only, click to copy)
Package Base: golfscript
Description: A simple stack based code golf language
Upstream URL: http://golfscript.com/golfscript
Licenses: MIT
Submitter: NGeorgescu
Maintainer: NGeorgescu
Last Packager: NGeorgescu
Votes: 1
Popularity: 0.000000
First Submitted: 2023-09-25 15:34 (UTC)
Last Updated: 2023-12-07 17:51 (UTC)

Latest Comments

maksverver commented on 2023-12-11 16:07 (UTC) (edited on 2023-12-11 16:07 (UTC) by maksverver)

Thanks for the update!

If you want to make a git-based package, please follow these guidelines: https://wiki.archlinux.org/title/VCS_package_guidelines

In particular:

  1. Add a "-git" suffix to the package name (this lets users know it's a development package).
  2. Use a git-URL as the source (this allows the package version to be derived automatically, and allows AUR helpers like yay to detect the package is out-of-date)

But I don't recommend that you do it for this package. A regular package is easier to use, so long as you don't mind bumping the version whenever the upstream version changes (which, as you mentioned, isn't often).

NGeorgescu commented on 2023-12-07 17:56 (UTC)

Hey Maks,

I went ahead and added it. Usually git packages don't seem to have checksums but I guess it's not a bad idea, esp. because this package hardly ever changes. (Last change It seems was >1 year ago).

maksverver commented on 2023-12-07 12:13 (UTC)

Nicholas, have you considered adding checksums to the PKGBUILD? This has two significant benefits that I can think of:

  1. It's more secure, obviously.
  2. It requires a pkgrel update whenever the source code changes. This is more work for the maintainer, but the benefit is that people who have the old package installed can know when it's out of date. Currently, there is no way to know when the package must be reinstalled.