lux-cli-pin(1)

πŸ“¦ version 0.48.0, in nixpkgs unstable

πŸ’– NAME πŸ’–

lux-cli-pin β€” pin an existing rock, preventing any updates to the package. This is lux-cli-pin(1), straight out of the General Commands Manual, and bestie it is literally the command for locking a rock in place so it stops getting updated πŸ’…

πŸ¦‹ SYNOPSIS πŸ¦‹

lux-cli pin [-b|--build] [--server] [-t|--test] [--extra-servers]
[-p|--package] [--namespace] [--lua-dir] [--lua-version] [--tree]
[--cache-dir] [--data-dir] [--variables] [--profile] [--verbose]
[--no-progress] [--no-prompt] [--preset] [--nvim] [--no-tfa] [--timeout]
[--max-jobs] [--no-luarc] [--no-wrap-bin] [--user-agent] [-h|--help]
[PACKAGE_REQ]

✨ DESCRIPTION ✨

okay so the whole vibe of lux-cli-pin is: you already have a rock, and you want to pin it, preventing any updates to the package. no cap, that is the job. It is the pin command, and it wants your existing rock to stay exactly where it is β€” iconic locking-in behavior, fr fr πŸŽ€

πŸ’… OPTIONS πŸ’…

okay bestie, here is the full flag menu, in order, no skipping 🫢

  • -b, --build <BUILD> β€” pin a development dependency. Also called dev.
  • --server <server> β€” fetch rocks/rockspecs from this server (takes priority over config file).
  • -t, --test <TEST> β€” pin a test dependency.
  • --extra-servers <extra-server> β€” fetch rocks/rockspecs from these servers in addition to the main server {n} (overrides any entries in the config file).
  • -p, --package <PACKAGE> β€” project to modify.
  • --namespace <namespace> β€” specify the luarocks server namespace to use.
  • --lua-dir <prefix> β€” specify the directory in which to install Lua if not found.
  • --lua-version <ver> β€” which Lua installation to use. {n} Valid versions are: '5.1', '5.2', '5.3', '5.4', '5.5', 'jit' and 'jit52'. {n} If not set, Lux will attempt to detect the Lua version: {n} - From the current project, if it has an exact Lua version requirement. {n} - From the Lua installation that is available on the PATH.
  • --tree <tree> β€” which tree to operate on. {n} In a workspace, this can be used to specify a detached workspace tree.
  • --cache-dir <cache-dir> β€” specifies the cache directory, e.g. for luarocks manifests.
  • --data-dir <data-dir> β€” specifies the data directory, {n} in which the default user install tree resides {n} (e.g. ~/.local/share/lux).
  • --variables <variable> β€” override config variables. {n} Example: lx -v "LUA=/path/to/lua" ...
  • --profile <profile> β€” the build profile to use when compiling packages. {n} Default: release.
    • possible values:
      • release
      • dev
  • --verbose β€” display verbose output of commands executed, enabling DEBUG logs. {n} To enable TRACE logs, set RUST_LOG=trace.
  • --no-progress β€” don't print any progress bars or spinners.
  • --no-prompt <NO_PROMPT> β€” skip prompts, selecting the default option. {n} Prompting is enabled by default in terminal/TTY environments.
    • possible values:
      • true
      • false
  • --preset <preset> β€” configure Lux for a specific environment. {n} Valid presets are: 'nvim'.
    • possible values:
      • nvim: Configure Lux for Neovim plugins
  • --nvim β€” [DEPRECATED] Configure lux for installing Neovim packages. {n} Use --preset nvim instead.
  • --no-tfa β€” disable prompts for two-factor authentication (2FA) codes. {n} It is strongly recommended to enable 2FA instead see (https://luarocks.org/settings/two-factor-auth).
  • --timeout <seconds> β€” timeout on network operations, in seconds. {n} 0 means no timeout (wait forever). Default is 30.
  • --max-jobs <MAX_JOBS> β€” maximum buffer size for parallel jobs, such as downloading rockspecs and installing rocks. 0 means no limit. Default is 0.
  • --no-luarc β€” do not generate or update a .luarc.json file when building {n} a project.
  • --no-wrap-bin β€” do not wrap Lua bin scripts.
  • --user-agent <USER_AGENT> β€” the user agent to set when making web requests. Default is "lux/<version>".
  • -h, --help β€” print help (see a summary with -h).
  • [PACKAGE_REQ] β€” installed package or dependency to pin. If pinning a dependency in a project, this should be the package name.

okay that's the page, bestie 🫢 β€” footer sign-off: source/version pin, manual lux-cli-pin(1), and the date slot is empty in this copy, no cap 🌈

πŸ“¦ where this page comes from