lux-cli-help-vendor(1)
π NAME π
okay so bestie, this is lux-cli-help-vendor(1) from the General Commands Manual β the manual name is literally lux-cli-help-vendor, and we're folding that in right at the top instead of making you read a boring header line π
lux-cli-help-vendor β vendor the dependencies of a project or RockSpec locally. When building or installing a package with the --vendor-dir option{n} or the [vendor_dir] config option, Lux will fetch sources from the <vendor-dir>{n} instead of from a remote server. That's the whole name-section tea, periodt ββ¨
β¨ SYNOPSIS β¨
lux-cli help vendor
π DESCRIPTION π
okay so here's the actual vibe: vendor the dependencies of a project or RockSpec locally. When you're building or installing a package with the --vendor-dir option{n} or the [vendor_dir] config option, Lux will fetch sources from the <vendor-dir>{n} instead of from a remote server. That's it β the vendor-dir gets the sources, the remote server does not, and Lux is just following the CLI option or config option you picked π«Άπ₯
no cap, that's the full behavior described here β keep those {n} bits exactly as they appear, they're part of the page's lore π
catch you later from the vendor footer of lux-cli-help-vendor(1) π β no date was included there, so I'm not inventing one; just sending manual-name love and dipping πβ¨
π¦ where this page comes from
- nixpkgs unstable: lux-cli 0.48.0
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms