1APT-CUDF(1) DOSE Tools APT-CUDF(1)
2
6 apt-cudf - CUDF solver integration for APT
7
9 solvername
10
12 apt-cudf translates back and forth among a CUDF-based dependency solver
13 and the protocol used by APT to talk with external dependency solvers.
14 apt-cudf therefore allows one to use any CUDF solver as an external
15 solver for APT.
16 apt-cudf relies on its "argv[0]" name to find the CUDF solver to
18 invoke. In common setups, you should have a CUDF solver specification
19 file under /usr/share/cudf/solvers/ for each installed CUDF solver. To
20 use one such solver with APT, you should create a symbolic link
21 pointing to /usr/bin/apt-cudf under /usr/lib/apt/solvers/ and call it
22 with the name of the CUDF solver you want to use.
23
25 -v
26 --verbose
27 Print debugging information during operation. Can be repeated.
28 -h
30 --help
31 Show usage information and exit.
32 --version
34 Show program's version and exit.
35 --dump
37 Dump the cudf universe and solution
38 --noop
40 Dump the cudf universe and solution and exit. This is useful to
41 generate a cudf universe from a edsp file
42 --conf
44 Use a configuration file. Default in /etc/apt-cudf.conf
45 -s <solver>
47 --solver <solver>
48 Specify the external solver to use.
49 -c <criteria>
51 --criteria <criteria>
52 Specify the optimization criteria in extended MISC 2012 syntax.
53 This value will be converted into the optimization criteria
54 language understood by the respective solver.
55 As an extension to the MISC 2012 syntax, a variation of the count()
57 measurement is supported by apt-cudf. The extension allows one to
58 minimize or maximize the number of packages in a set that have an
59 EDSP field matching a regular expression. Two formats exist. The
60 first searches for a plain string within the EDSP field value:
61 count(selector,field:=/plain/)
63 While the second one understands the regular expression syntax of
65 the OCaml Re_pcre module:
66 count(selector,field:~/regex/)
68 The regex or plain string are delimitered by any character (the
70 slash was chosen in both above examples) but that character must
71 not be part of the regex or plain string itself (there is no
72 escaping mechanism).
73 This option cannot be used together with the --criteria-plain
75 option.
76 --criteria-plain <criteria>
78 This optimization criteria is passed directly to the solver without
79 any prior parsing.
80 This option cannot be used together with the --criteria option.
82 -e
84 --explain
85 Print a human-readable summary of the solution.
86 --native-arch
88 Speficy the native architecture to be used in the edsp -> cudf
89 translation. By default apt-cudf uses apt-config to deduce the
90 native architecture. This option is useful if the edsp was
91 generated on a machine with a different architecture.
92 --foreign-archs
94 A comma-separated list of foreign architectures to be used in the
95 edsp -> cudf translation
96
98 Find a solution for installing the package ghc which minimizes the
99 packages from experimental:
100 APT_EDSP_DUMP_FILENAME=/tmp/dump.edsp apt-get --simulate install --solver dump -o APT::Solver::Strict-Pinning=false ghc
102 apt-cudf -v --solver=aspcud -c "-count(solution,APT-Release:=/a=experimental/),-removed,-changed,-new" /tmp/dump.edsp
103 Usually apt-cudf is not called directly by the user but indirectly by
105 apt-get. So the above would become:
106 apt-get --simulate install --solver aspcud -o APT::Solver::Strict-Pinning=false -o APT::Solver::aspcud::Preferences="-count(solution,APT-Release:=/a=experimental/),-removed,-changed,-new" ghc/experimental
108
110 apt-get(8), update-cudf-solvers(8), README.cudf-solvers
111 <file:///usr/share/doc/apt-cudf/README.cudf-solvers>, README.Debian
112 <file:///usr/share/doc/apt-cudf/README.Debian>
113
115 Copyright: (C) 2011 Pietro Abate <pietro.abate@pps.jussieu.fr>
116 Copyright: (C) 2011 Stefano Zacchiroli <zack@debian.org>
117 License: GNU Lesser General Public License (GPL), version 3 or above
119 2020-09-02 APT-CUDF(1)