archlinux-pkgbuild/interpreted-languages

Generate Arch Linux PKGBUILD templates for interpreted language packages.

6|Updated Jan 14, 2020
One-click install
npx skills add https://github.com/SteamedFish/dotfiles --skill archlinux-pkgbuild-interpreted-languages
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archlinux-pkgbuild/interpreted-languages
Source: https://github.com/SteamedFish/dotfiles/tree/main/.config/opencode/skills/archlinux-pkgbuild/interpreted-languages
Command: npx skills add https://github.com/SteamedFish/dotfiles --skill archlinux-pkgbuild-interpreted-languages

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the complex process of packaging interpreted language ecosystems (like Node.js, Python, Perl, PHP, Ruby, R, Shell, and Lisp) for the Arch Linux package manager (pacman).

Core Features & Use Cases

  • Language-Specific Packaging: Provides detailed rules, templates, and common issue resolutions for each supported interpreted language.
  • Dependency Management: Guides on correctly specifying dependencies for runtimes and build tools.
  • Installation Paths: Ensures packages are installed to the correct system locations according to Arch Linux standards.
  • Use Case: You need to create an Arch Linux package for a Python library that uses native extensions. This Skill provides the PKGBUILD template, explains the arch=('x86_64') requirement, and lists necessary makedepends like python-build.

Quick Start

Use the archlinux-pkgbuild/interpreted-languages skill to generate a PKGBUILD for a Node.js npm package.

Frequently Asked Questions about archlinux-pkgbuild/interpreted-languages

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I package Python libraries with native extensions for Arch Linux?

Packaging Python libraries with native extensions for Arch Linux requires specifying arch=('x86_64') in the PKGBUILD and including necessary makedepends like python-build to manage the build process correctly.

What are the correct installation paths for Node.js npm packages in pacman?

Correct installation paths for Node.js npm packages in pacman ensure system integration according to Arch Linux standards, preventing conflicts and facilitating reproducible builds across user environments.

How do I specify dependencies for Ruby or Perl packages in an Arch Linux PKGBUILD?

Specifying dependencies for Ruby or Perl packages in an Arch Linux PKGBUILD involves correctly listing runtime and build tool dependencies to ensure the interpreted language software functions properly upon installation.

Does this packaging guidance cover interpreted languages like R, PHP, and Lisp?

Yes, this packaging guidance covers interpreted languages like R, PHP, and Lisp, detailing specific package naming conventions, build processes, and common pitfalls for each ecosystem to ensure system integration.

What is the best way to avoid common pitfalls when creating PKGBUILDs for interpreted languages?

The best way to avoid common pitfalls when creating PKGBUILDs for interpreted languages is to follow comprehensive guidelines and templates that detail correct dependency management and installation paths for each specific ecosystem.

Why do I need to specify arch=('x86_64') for some Python packages in Arch Linux?

You need to specify arch=('x86_64') for Python packages with native extensions because they compile architecture-specific binaries, requiring correct build processes and makedepends to ensure reproducible builds.