Xlings Quickstart

2) Verify installation

xlings help
xim -h

If xlings/xim is not found, reload shell profile (source ~/.bashrc) and retry.

Common Usage and Scenarios

Use these commands first for daily operations:

xlings install gcc@15
xlings remove gcc
xlings search gcc
xlings update gcc

Use xim directly when you need lower-level package-index operations:

xim -s gcc
xim -l
xim --update index

Scenario guide:

• Need one tool quickly: xlings install <name> or xlings install <name>@<version>.
• Need to inspect candidates first: xlings search <keyword> / xim -s <keyword>.
• Need to cleanup: xlings remove <name>.
• Need to refresh package metadata: xim --update index.

Namespace and Custom Index

Package name forms to support:

• <name>
• <name>@<version>
• <namespace>:<name>
• <namespace>:<name>@<version>

For custom or self-hosted index repos, register sub-indexrepo with namespace binding:

xim --add-indexrepo <namespace>:<git-repo-url>
xim --update index

For ad-hoc package file onboarding:

xim --add-xpkg /path/to/your.xpkg.lua
# or
xim --add-xpkg https://your-host/path/to/your.xpkg.lua

Multi-Version and Subos Isolation

Use xvm through xlings for version switching:

xlings use <tool>
xlings use <tool> <version>

Use subos commands when workloads need isolated env views:

xlings subos list
xlings subos new <env-name>
xlings subos use <env-name>

Operational model to remember:

• Package store can be shared globally.
• Active tool mapping/version visibility is managed per subos via xvm metadata.
• Namespace + version selector avoids collisions for similarly named packages.

References

• Read references/commands.md for command cheatsheet.
• Read references/links.md for project, index, docs, and community URLs.