archlinux-pkgbuild

Category: Tools & Productivity | Uploader: SteamedFish | Downloads: 0 | Version: v1.0（Latest）

Use when creating or reviewing Arch Linux PKGBUILD files, preparing AUR submissions, or fixing namcap/FHS/dependency issues in package metadata and build scripts.

Changelog: Source: GitHub https://github.com/SteamedFish/dotfiles

Directory Structure

Current level: .config/agents/skills/archlinux-pkgbuild/

📁 build-systems/
- 📄 SKILL.md 3.8 KB
- 📄 SKILL.zh-CN.md 3.9 KB
📁 compiled-languages/
- 📄 SKILL.md 14.6 KB
- 📄 SKILL.zh-CN.md 14.7 KB
📁 cross-platform/
- 📄 SKILL.md 9.4 KB
- 📄 SKILL.zh-CN.md 9.7 KB
📁 desktop-integration/
- 📄 SKILL.md 7.2 KB
- 📄 SKILL.zh-CN.md 7.2 KB
📁 interpreted-languages/
- 📄 SKILL.md 23.1 KB
- 📄 SKILL.zh-CN.md 23.1 KB
📁 system-packages/
- 📄 SKILL.md 20.7 KB
- 📄 SKILL.zh-CN.md 20.3 KB
📁 systemd-services/
- 📄 SKILL.md 16.3 KB
- 📄 SKILL.zh-CN.md 16.1 KB
📁 vcs-packages/
- 📄 SKILL.md 18.2 KB
📄 advanced-workflow-and-build.md 15.0 KB
📄 advanced-workflow-and-build.zh-CN.md 15.0 KB
📄 aur-publishing-and-release-tracking.md 6.5 KB
📄 aur-publishing-and-release-tracking.zh-CN.md 6.4 KB
📄 clean-chroot-reference.md 4.3 KB
📄 clean-chroot-reference.zh-CN.md 4.2 KB
📄 config-file-handling.md 5.5 KB
📄 config-file-handling.zh-CN.md 5.4 KB
📄 fhs-and-vendor-config.md 5.7 KB
📄 fhs-and-vendor-config.zh-CN.md 5.8 KB
📄 pkgbuild-template.sh 1.2 KB
📄 policy-quality-and-install-scripts.md 14.1 KB
📄 policy-quality-and-install-scripts.zh-CN.md 13.9 KB
📄 shared-language-packaging-baseline.md 1.1 KB
📄 shared-language-packaging-baseline.zh-CN.md 1.0 KB
📄 SKILL.md 5.4 KB
📄 SKILL.zh-CN.md 5.1 KB
📄 validation-guide.md 4.8 KB

SKILL.md

---
name: archlinux-pkgbuild
description: Use when creating or reviewing Arch Linux PKGBUILD files, preparing AUR submissions, or fixing namcap/FHS/dependency issues in package metadata and build scripts.
---

# Arch Linux PKGBUILD Creation

## Overview

Use this skill as the default workflow for PKGBUILD work.  
Core rule: do not claim packaging is complete until `namcap` passes for both `PKGBUILD` and built package artifacts.

This skill is intentionally concise. Load sub-skills and reference docs only when needed.

## When to Use

- Writing a new PKGBUILD from upstream source or binary release.
- Updating package version, dependencies, install behavior, or architecture metadata.
- Debugging `namcap` warnings/errors.
- Preparing `.SRCINFO` and AUR push.

## Sub-Skills

| Sub-skill | Trigger |
|---|---|
| `archlinux-pkgbuild/vcs-packages` | `-git/-svn/-hg/-bzr/-darcs` packages, `pkgver()` logic |
| `archlinux-pkgbuild/systemd-services` | Services, `sysusers.d`, `tmpfiles.d`, sandboxing |
| `archlinux-pkgbuild/compiled-languages` | Go/Rust/Java/Haskell/OCaml/Pascal builds |
| `archlinux-pkgbuild/interpreted-languages` | Python/Node/Ruby/PHP/Perl/R/Shell/Lisp packages |
| `archlinux-pkgbuild/build-systems` | CMake or Meson projects |
| `archlinux-pkgbuild/cross-platform` | Wine/MinGW/Electron/.NET/Mono packaging |
| `archlinux-pkgbuild/desktop-integration` | GNOME/KDE/Eclipse/font integration |
| `archlinux-pkgbuild/system-packages` | DKMS/kernel/lib32/nonfree/webapp/split packages |

## Mandatory Workflow

```mermaid
flowchart TD
    A[Check existing packages] --> B[Write or update PKGBUILD]
    B --> C[Run namcap on PKGBUILD]
    C --> D{Passes?}
    D -->|No| B
    D -->|Yes| E{devtools available?}
    E -->|Yes| F[Build in clean chroot]
    E -->|No| G[Build with makepkg and warn]
    F --> H[Run namcap on built package]
    G --> H
    H --> I{Passes?}
    I -->|No| B
    I -->|Yes| J[Test install]
    J --> K[Generate .SRCINFO]
```

## Quick Reference

### 0. Package split decision

| Scenario | Rule |
|----------|------|
| Multiple packages built from **same source** | Use **split packages** in a single PKGBUILD (`pkgbase` + `pkgname=()` array) |
| Each package comes from **different source** | Create **separate PKGBUILDs**, one per package |

Use `archlinux-pkgbuild/system-packages` for the split-package mechanics (`pkgbase`, `package_name()` functions).

### 1. Existence check

```bash
pacman -Ss '^pkgname$'
yay -Ss '^pkgname$'   # or paru -Ss
```

If official repo has it, do not create duplicate AUR package.

### 2. Build method

| Method | Use case |
|---|---|
| `extra-x86_64-build` (preferred) | AUR submission, dependency correctness |
| `makepkg -f` (fallback) | Local prototyping only |

If fallback is used, explicitly warn that dependencies may be incomplete due to non-chroot build.

### 3. Validation (required)

```bash
namcap PKGBUILD
namcap *.pkg.tar.zst
```

Recommended deep checks:

```bash
namcap -i PKGBUILD
namcap -i *.pkg.tar.zst
```

### 4. Minimum PKGBUILD quality gates

| Item | Rule |
|---|---|
| Paths | Never install to `/usr/local`; package files go under `/usr` |
| Vendor config | Put package-owned defaults in `/usr/lib`, not `/etc` |
| Dependencies | List direct runtime/build deps only; no transitive padding. Do not include packages from `base` in `depends`/`optdepends` or `base-devel` in `makedepends` — both groups are assumed present |
| Checksums | Use `sha256sums`/`sha512sums`/`b2sums`; `SKIP` only for VCS sources |
| Arch field | `any` only for architecture-independent packages |
| Shell vars | Quote `"$pkgdir"` and `"$srcdir"` |
| Config files | User-editable `/etc` files must be in `backup=()` |

### 5. Architecture policy

- Source-built packages: prefer `x86_64` + `aarch64` when both can be validated.
- Binary packages: only declare architectures that upstream actually publishes.
- If only one architecture is tested, keep `arch=()` limited to tested architectures.

### 6. AUR finalization

```bash
makepkg --printsrcinfo > .SRCINFO
```

Track: `PKGBUILD`, `.SRCINFO`, patches, `.install`, service/tmpfiles/sysusers files.  
Ignore build artifacts (`pkg/`, `src/`, `*.pkg.tar.*`, `.BUILDINFO`, `.PKGINFO`, `.MTREE`, `.INSTALL`).

## Supporting References

- `advanced-workflow-and-build.md`: detailed workflow, dependency, architecture, build, and validation execution
- `aur-publishing-and-release-tracking.md`: detailed AUR push workflow, `.SRCINFO`/`.gitignore`, and nvchecker/pkgctl usage
- `policy-quality-and-install-scripts.md`: red flags, quality gates, configuration handling, and `.install` script patterns
- `pkgbuild-template.sh`: annotated baseline template
- `validation-guide.md`: `namcap` interpretation and fix patterns
- `fhs-and-vendor-config.md`: correct install destinations
- `config-file-handling.md`: `backup=()` and sensitive file permissions
- `clean-chroot-reference.md`: advanced `devtools`/chroot workflows

## Common Mistakes

- Submitting packages built only with local `makepkg` without warning.
- Using `/etc` for vendor defaults that belong in `/usr/lib`.
- Forgetting to regenerate `.SRCINFO` after dependency/version updates.
- Declaring unsupported architectures in binary packages.

## Resources

- https://wiki.archlinux.org/title/Arch_package_guidelines
- https://man.archlinux.org/man/PKGBUILD.5
- https://wiki.archlinux.org/title/Namcap
- https://wiki.archlinux.org/title/AUR_submission_guidelines
- https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

archlinux-pkgbuild

Directory Structure

SKILL.md

Report

Notice