Skip to content

yay

Recipe card from the charly-tools plugin (Images — the deployable catalog).

Property Value
Install files charly.yml (run: step)
Depends none

PAC: base-devel, git

The run: step downloads the latest yay binary from GitHub releases:

# yay charly.yml — steps are an ordered list under plan:
yay:
candy:
version: 2026.144.1443
plan:
- run: download the latest yay binary from GitHub releases
command: |
URL=$(curl -fsSL https://api.github.com/repos/Jguer/yay/releases/latest \
| grep -o "https://github.com/Jguer/yay/releases/download/[^\"]*_${BUILD_ARCH}.tar.gz")
curl -fsSL "$URL" | tar -xzf - -C /usr/local/bin --strip-components=1 --wildcards '*/yay'
run_as: root

Architecture-aware: ${BUILD_ARCH} expands to the correct binary for x86_64 or aarch64 at build time.

Installs the yay AUR helper, which enables the aur: package format in charly.yml. Any candy with an aur: section requires a builder that has the yay candy (and builds: [aur] capability). The base-devel and git packages are prerequisites for building AUR packages.

# charly.yml — typically in a builder image (compose the candy inline)
my-builder:
candy:
base: arch
candy: [yay]

Not used directly in end-user boxes. Instead, it’s part of the builder image that compiles AUR packages during multi-stage builds.

Use when the user asks about:

  • AUR package support in OpenCharly
  • The yay candy or AUR helper installation
  • How aur: packages in charly.yml get built
  • The arch-builder box’s AUR capability
  • /charly-image:layer — candy authoring reference (charly.yml schema, plan-step verbs, service declarations)
  • /charly-check:check — declarative testing (check: block, charly check box, charly check live)