APT-CUDF.CONF(5)
β¨ apt-cudf.conf β the config file glow-up β¨
okay bestie, we're in section 5 of the manual today (that's the "file formats" section, so this is literally about a config file, not a command π ), from the DOSE Tools crew.
πΈ NAME πΈ
apt-cudf.conf β it's the configuration file for apt-cudf, periodt.
π¦ DESCRIPTION π¦
So here's the vibe: this config file lets you set default optimization criteria for all the solvers that apt-cudf knows about. That's it, that's the whole assignment. One file, set your defaults, serve looks for every solver at once. iconic behavior, honestly.
π SYNTAX π
the way this file is just lil keyword lines... obsessed. here's every shape a line can take:
π solver lines
solver: <solver list> | '*'
You hand it a comma-separated list of solvers. And if you use the * character? That makes the optimization criteria the default for every solver that doesn't have a more specific definition β a little catch-all moment, no cap. π
π action defaults
upgrade: <optimization criteria>
dist-upgrade: <optimization criteria>
install: <optimization criteria>
remove: <optimization criteria>
These are the default optimization criteria associated to apt-get actions β so yes, upgrade, dist-upgrade, install, remove, each get their own line. π«
β οΈ heads up though β the optimization criteria is solver specific. If you specify an incorrect criteria, the underlying cudf solver is gonna throw an error at you. π So please, please go read the solver's own man page for the correct syntax before you type anything. iykyk.
π shortcuts
trendy: <optimization criteria>
paranoid: <optimization criteria>
<keyword>: <optimization criteria>
This is where it gets fun π§ β you get to define a shortcut for an optimization criteria. Then apt-get can use that shortcut to pass a specific optimization criteria along to a cudf solver. look at you, being efficient.
like, for example:
apt-get install gnome --solver aspcud -o "APT::Solver::aspcud::Preferences=trendy"
see?? trendy doing all the heavy lifting. main character energy fr fr. π
π₯ EXAMPLE π₯
here's a whole little config serving realness:
solver: mccs-cbc , mccs-lpsolve
upgrade: -lex[-new,-removed,-notuptodate]
dist-upgrade: -lex[-notuptodate,-new]
install: -lex[-removed,-changed]
remove: -lex[-removed,-changed]
trendy: -lex[-removed,-notuptodate,-unsat_recommends,-new]
paranoid: -lex[-removed,-changed]
and then the catch-all * version, for when you want these to hit everybody:
solver: *
upgrade: -new,-removed,-notuptodate
dist-upgrade: -notuptodate,-new
install: -removed,-changed
remove: -removed,-changed
trendy: -removed,-notuptodate,-unsat_recommends,-new
paranoid: -removed,-changed
see how the second block drops the -lex[...] wrapper? cute. copy responsibly tho. π
π SEE ALSO π
go read these next, bestie, they're the supporting cast:
apt-cudf(8)apt-get(8)update-cudf-solvers(8)README.cudf-solvers<file:///usr/share/doc/apt-cudf/README.cudf-solvers>README.Debian<file:///usr/share/doc/apt-cudf/README.Debian>
π AUTHOR π
giving credit where it's due, as we always do:
- Copyright: (C) 2011 Pietro Abate <pietro.abate@pps.jussieu.fr>
- Copyright: (C) 2011 Stefano Zacchiroli <zack@debian.org>
License: GNU Lesser General Public License (GPL), version 3 or above
and that's the whole page!! π«Ά this was the apt-cudf(5) manual page from the DOSE Tools era, dated 2026-07-06 β love that for us. now go configure your solvers and slay πβ¨
π¦ where this page comes from
- ubuntu stonking: apt-cudf 7.0.0-8build2 Β· LGPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms