AUR

Publish to the Arch User Repository

Anodizer generates Arch Linux PKGBUILD and .SRCINFO files and pushes them to the Arch User Repository via SSH. Two package types are supported:

• Binary packages (-bin) install prebuilt binaries from your release archives. Configured via publish.aur.
• Source packages build from source using cargo build. Configured via publish.aur_source (per-crate) or the top-level aur_sources array (project-wide).

Binary packages (publish.aur)

Binary packages download a prebuilt archive from your release and install the binary. The package name defaults to <crate>-bin following AUR convention.

Minimal config

crates:
  - name: myapp
    publish:
      aur:
        git_url: "ssh://aur@aur.archlinux.org/myapp-bin.git"

Config fields

Full example

crates:
  - name: myapp
    publish:
      aur:
        git_url: "ssh://aur@aur.archlinux.org/myapp-bin.git"
        name: myapp-bin
        description: "A fast CLI tool"
        homepage: "https://github.com/myorg/myapp"
        license: MIT
        depends:
          - glibc
        optdepends:
          - "bash-completion: shell completions"
        maintainers:
          - "Jane Doe <jane@example.com>"
        private_key: "{{ .Env.AUR_SSH_KEY }}"
        skip_upload: auto

Generated PKGBUILD

Anodizer generates a PKGBUILD with:

• Per-architecture source arrays (source_x86_64, source_aarch64, etc.) with SHA-256 checksums
• Automatic architecture detection from your Linux build artifacts (x86_64, aarch64, i686, armv7h)
• Version strings with hyphens replaced by underscores (AUR pkgver requirement)
• Download URLs with the version substituted as ${pkgver} for AUR compatibility
• A .SRCINFO file generated alongside the PKGBUILD (no makepkg --printsrcinfo dependency)

The default package() function installs the binary to /usr/bin:

package() {
    install -Dm755 "$srcdir/myapp" "$pkgdir/usr/bin/myapp"
}

Override this with the package field when your archive has a different structure.

Source packages (publish.aur_source)

Source packages download a source tarball and build from source using cargo build. The package name does not have a -bin suffix.

Minimal config

crates:
  - name: myapp
    publish:
      aur_source:
        git_url: "ssh://aur@aur.archlinux.org/myapp.git"

Config fields

Full example

crates:
  - name: myapp
    publish:
      aur_source:
        git_url: "ssh://aur@aur.archlinux.org/myapp.git"
        name: myapp
        description: "A fast CLI tool"
        homepage: "https://github.com/myorg/myapp"
        license: MIT
        depends:
          - glibc
        makedepends:
          - rust
          - cargo
        maintainers:
          - "Jane Doe <jane@example.com>"
        private_key: "{{ .Env.AUR_SSH_KEY }}"
        skip_upload: auto

Generated source PKGBUILD

The default source PKGBUILD downloads the GitHub release source tarball and builds with Cargo:

build() {
  cd "$srcdir/myapp-$pkgver"
  cargo build --release --locked
}

package() {
  cd "$srcdir/myapp-$pkgver"
  install -Dm755 "target/release/myapp" "$pkgdir/usr/bin/myapp"
}

If no url_template is set, the source URL defaults to:

https://github.com/<owner>/<project>/archive/refs/tags/<tag>.tar.gz

The owner and project are derived from GitURL and ProjectName template variables.

Top-level aur_sources

For project-wide source packages not tied to a specific crate, use the top-level aur_sources array. This follows the same schema as publish.aur_source and accepts multiple entries:

aur_sources:
  - name: myapp
    git_url: "ssh://aur@aur.archlinux.org/myapp.git"
    description: "A fast CLI tool"
    license: MIT
    makedepends:
      - rust
      - cargo
  - name: myapp-git
    git_url: "ssh://aur@aur.archlinux.org/myapp-git.git"
    description: "A fast CLI tool (git version)"
    license: MIT

Each entry generates its own PKGBUILD and .SRCINFO, written to dist/aur_source/<name>/ and optionally pushed to the configured AUR git URL.

SSH key setup

AUR publishing requires SSH access. To configure this:

1. Generate an SSH key (if you do not already have one for AUR):

   ssh-keygen -t ed25519 -f ~/.ssh/aur -N ""

2. Add the public key to your AUR account at https://aur.archlinux.org/account under "SSH Public Key".

3. Reference the private key in your config:

   publish:
     aur:
       git_url: "ssh://aur@aur.archlinux.org/myapp-bin.git"
       private_key: "{{ .Env.AUR_SSH_KEY }}"

4. In CI, store the private key as a secret and expose it as an environment variable:

   # GitHub Actions example
   env:
     AUR_SSH_KEY: ${{ secrets.AUR_SSH_KEY }}

Alternatively, use git_ssh_command for full control over the SSH invocation:

publish:
  aur:
    git_url: "ssh://aur@aur.archlinux.org/myapp-bin.git"
    git_ssh_command: "ssh -i /path/to/key -o StrictHostKeyChecking=no"

If neither private_key nor git_ssh_command is set, Anodizer uses the system default SSH configuration (e.g. ~/.ssh/config, ssh-agent).

skip_upload behavior

The skip_upload field controls whether Anodizer pushes to the AUR git repo:

The disable field works similarly but skips the entire stage, including PKGBUILD generation.