aspcud(1)

πŸ“¦
version 1.9.6 Β· 2 versions
  • 1.9.6 Β· alpine 3.24, debian bookworm, debian trixie, nixos 26.05, nixpkgs unstable, ubuntu noble, ubuntu resolute, ubuntu stonking (latest)
  • 1.9.5 Β· ubuntu jammy
, in alpine 3.24, debian bookworm, debian trixie, nixos 26.05, nixpkgs unstable, ubuntu noble, ubuntu resolute, ubuntu stonking

πŸ’… aspcud β€” the manual page, but make it make sense

okay bestie, welcome to aspcud(1), from the USER COMMANDS section of the manual. this is the whole vibe, let me walk you through it 🫢


✨ NAME ✨

aspcud β€” solve dependencies between packages πŸ’–

like, it literally figures out which packages go together. no cap.


🌸 SYNOPSIS 🌸

aspcud [OPTION]... [INPUT-FILE] [OUTPUT-FILE] [CRITERION]

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so aspcud solves package installation / removal / upgrade problems, and those problems get expressed in the CUDF format. it's intended to be called by package installers, but bestie, it can also be used independently. main character energy fr.

and here's the thing β€” if the tool can't find a solution? it writes "FAIL" to the output file. that's it. that's the message. 😭


πŸŽ€ ARGUMENTS πŸŽ€

these are the command-line arguments it accepts, and yes, all three of them matter:

  • INPUT-FILE β€” the pathname of the file holding the problem specification in CUDF format (both the universe and the request, the whole package πŸ“). if it's absent, the specification is read from stdin.
  • OUTPUT-FILE β€” the pathname of the file the solution gets written into, in CUDF output format. if the file doesn't exist, it gets created; if it already exists, it gets overwritten without warning 😳 (yes, no warning, no take-backs, she does not ask). if it's absent, output goes to stdout.
  • CRITERION β€” selects the optimization criterion. to get a list of supported criteria, go look at the -c option of cudf2lp(1). if it's absent, the paranoid criterion is used. also, heads up: the criterion can be passed via the --criterion option too. two ways, same slay πŸ’…

✨ OPTIONS ✨

aspcud supports these options, and yes, we're doing all of them:

  • -h, --help β€” print help text, and default configurations and paths
  • -v, --version β€” print version and license information
  • -c, --criterion CRIT β€” set the optimization criterion
  • -s, --solver-option OPT β€” append clasp option OPT (can be given multiple times); if at least one clasp option is given, then default search options are not used
  • -g, --grounder-option OPT β€” append gringo option OPT (can be given multiple times)
  • -e, --encoding ENC β€” append encoding ENC (can be given multiple times); if at least one encoding is given, then the default encoding is not used
  • -p, --preprocessor-option OPT β€” append cudf2lp option OPT (can be given multiple times)
  • -S, --solver SOL β€” path to solver (clasp)
  • -G, --grounder GRD β€” path to grounder (gringo)
  • -P, --preprocessor PRE β€” path to cudf preprocessor (cudf2lp)
  • -V, --verbosity N β€” set the verbosity level
  • -d, --debug β€” do not cleanup temporary files
ngl the -s and -e ones are sneaky β€” the second you pass even one of them, the defaults dip out. no defaults, no problem, but know it πŸ’€

🌈 ENVIRONMENT VARIABLES 🌈

aspcud uses temporary files, periodt. these get put into the folder indicated by the environment variable TMPDIR or, if that's not set, by the POSIX constant P_tmpdir. πŸ’–


πŸ‘‘ AUTHOR πŸ‘‘

aspcud has been written by Roland Kaminski and Martin Gebser. legends, honestly. 🫢


πŸ’œ SEE ALSO πŸ’œ


and that's the whole page, bestie β€” go solve some dependencies, you're literally the solver now ✨

this was Version 1.9.6, dated May 01, 2022. mwah, go off πŸŽ€πŸ’…

πŸ“¦ where this page comes from