English | 简体中文
The official package index of xlings: recipes for compilers, runtimes, tools and environments, on Linux, macOS and Windows, x86_64 and aarch64.
curl -fsSL https://d2learn.org/xlings-install.sh | bashirm https://d2learn.org/xlings-install.ps1.txt | iexxlings search gcc
xlings install gcc -y
xlings updateBrowse every package, its versions and commands at index.xlings.org.
- Copy the template to
pkgs/<first letter>/<name>.lua. - Add
tests/<first letter>/test_<name>.py. - Open a pull request — Adding a package is the whole path.
The format is XPackage V2; all documentation is in docs/.
An agent (Claude Code, Cursor, Copilot, ...) can do the whole path; the skills
in .agents/skills/ hold the rules it must follow. Give it:
Read the README and docs/10-adding-a-package.md of
https://github.com/openxlings/xim-pkgindex, and follow
.agents/skills/xpkg-creater/SKILL.md and .agents/skills/pr-workflow/SKILL.md:
add the package <name> (upstream: <url>) for every platform and architecture
it publishes, with its test, verify it in an isolated XLINGS_HOME, then open
a pull request with what you ran.
Review its pull request as you would anyone's: the resources, the sha256s, and that the install ran.
| Repository | Namespace | For |
|---|---|---|
| xim-pkgindex-template | your own | a self-hosted, mirrored or private index |
| xim-pkgindex-fromsource | fromsource |
packages built from source |
| xim-pkgindex-d2x | d2x |
d2x course projects |