dselect.8 16 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382
  1. .TH DSELECT 8 "July 2001" "Debian Project" "Debian"
  2. .SH NAME
  3. dselect \- Debian package management frontend
  4. .SH SYNOPSIS
  5. .B dselect
  6. [\-\-admindir <directory>] [\-\-help] [\-\-version] [\-\-licence | \-\-license]
  7. [\-\-expert] [\-\-debug | \-D <file>] [\fI<action>\fP]
  8. .SH DESCRIPTION
  9. .B dselect
  10. is the primary user interface for managing packages on a Debian system.
  11. At the \fBdselect\fP main menu, the system administrator can:
  12. \- Update the list of available package versions,
  13. \- View the status of installed and available packages,
  14. \- Alter package selections and manage dependencies,
  15. \- Install new packages or upgrade to newer versions.
  16. .PP
  17. .B dselect
  18. operates as a front-end to \fBdpkg(8)\fP, the low-level debian package
  19. handling tool. It features a full-screen package selections manager
  20. with package depends and conflicts resolver. When run with adminitrator
  21. priviledges, packages can be installed, upgraded and removed. Various
  22. access methods can be configured to retrieve available package version
  23. information and installable packages from package repositories.
  24. Depending on the used access method, these repositories can be public
  25. archive servers on the internet, local archive servers or cdroms.
  26. The recommended access method is \fIapt\fP, which is provided by the
  27. package \fBapt\fP.
  28. .PP
  29. Normally \fBdselect\fP is invoked without parameters. An interactive
  30. menu is presented, offering the user a list of actions. If an action
  31. is given as argument, then that action is started immediately. Several
  32. commandline parameters are still available to modify the running behaviour
  33. of \fBdselect\fP or show additional information about the program.
  34. .SH OPTIONS
  35. All options can be specified both on the commandline and in the \fBdselect\fP
  36. configuration file \fI/etc/dpkg/dselect.cfg\fP. Each line in the
  37. configuration file is either an option (exactly the same as the
  38. commandline option but without leading dashes) or a comment (if it starts
  39. with a \fB#\fR).
  40. .br
  41. .TP
  42. .B --admindir <directory>
  43. Changes the directory where the dpkg `status', `available' and similar
  44. files are located. This defaults to \fI/var/lib/dpkg\fP
  45. and normally there shouldn't be any need to change it.
  46. .TP
  47. .B --debug <file> | -D<file>
  48. Turn on debugging. Debugging information is sent to \fI<file>\fP.
  49. .TP
  50. .B --expert
  51. Turns on expert mode, i.e. doesn't display possibly annoying help
  52. messages.
  53. .TP
  54. .B --help
  55. Print a brief help text and exit successfully.
  56. .TP
  57. .B --licence | --license
  58. Displays the \fBdselect\fP copyright and license information and exits
  59. successfully.
  60. .TP
  61. .B --version
  62. Print version information and exit successfully.
  63. .SH USAGE
  64. When
  65. .B dselect
  66. is started interactively, it prompts the user with a menu of available
  67. actions:
  68. .SS access
  69. Choose and configure an access method to access package repositories.
  70. .sp
  71. By default, \fBdselect\fP provides several methods such
  72. as \fIfloppy\fP, \fIharddisk\fP or \fIcdrom\fP, but other packages
  73. may provide additional methods, eg. the \fIapt\fP access method provided
  74. by the \fBapt\fP package or \fImulti_cd\fP by the \fBdpkg-multicd\fP
  75. package.
  76. .sp
  77. The use of the \fIapt\fP access method is strongly recommended.
  78. .sp
  79. .SS update
  80. Refresh the available packages database.
  81. .sp
  82. Retrieves a list of available package versions from the package
  83. repository, configured for the current access method, and update
  84. the dpkg database. The package lists are commonly provided by the
  85. repository as files named \fBPackages\fP or \fBPackages.gz\fP.
  86. These files can be generated by repository maintainers, using the
  87. program \fBdpkg-scanpackages(8)\fP.
  88. .sp
  89. Details of the update action depend on the access method's implementation.
  90. Normally the process is straightforward and requires no user interaction.
  91. .sp
  92. .SS select
  93. View or manage package selections and dependencies.
  94. .sp
  95. This is the main function of \fBdselect\fP. In the select screen, the
  96. user can review a list of all available and installed packages. When run
  97. with administrator privileges, it is also possible to interactively
  98. change packages selection state. \fBdselect\fP tracks the implications
  99. of these changes to other depending or conflicting packages.
  100. .sp
  101. When a conflict or failed depends is detected, a dependency resolution
  102. subscreen is prompted to the user. In this screen, a list of conflicting
  103. or depending packages is shown, and for each package listed, the reason
  104. for its listing is shown. The user may apply the suggestions proposed
  105. by \fBdselect\fP, override them, or back out all the changes, including
  106. the ones that created the unresolved depends or conflicts.
  107. .sp
  108. The use of the interactive package selections management screen is
  109. explained in more detail below.
  110. .sp
  111. .SS install
  112. Installs selected packages.
  113. .sp
  114. The configured access method will fetch installable or upgradable packages
  115. from the relevant repositories and install these using \fBdpkg\fP.
  116. Depending on the implementation of the access method, all packages can
  117. be prefetched before installation, or fetched when needed.
  118. Some access methods may also remove packages that were marked for removal.
  119. .sp
  120. If an error occurred during install, it is usually advisable to run
  121. install again. In most cases, the problems will disappear or be solved.
  122. If problems persist or the installation performed was incorrect, please
  123. investigate into the causes and circumstances, and file a bug in the
  124. Debian bug tracking system. Instructions on how to do this can be found
  125. at http://bugs.debian.org/ or by reading the documentation
  126. for \fBbug(1)\fP or \fBreportbug(1)\fP, if these are installed.
  127. .sp
  128. Details of the install action depend on the access method's implementation.
  129. The user's attention and input may be required during installation,
  130. configuration or removal of packages. This depends on the maintainer
  131. scripts in the package. Some packages make use of the \fBdebconf(8)\fP
  132. library, allowing for more flexible or even automated installation
  133. setups.
  134. .sp
  135. .SS config
  136. Configures any previously installed, but not fully configured packages.
  137. .sp
  138. .SS remove
  139. Removes or purges installed packages, that are marked for removal.
  140. .sp
  141. .SS quit
  142. Quit \fBdselect\fP
  143. .sp
  144. Exits the program with zero (succesful) errorcode.
  145. .sp
  146. .SH Package selections management
  147. .sp
  148. .SS Introduction
  149. .sp
  150. .B dselect
  151. directly exposes
  152. the administrator to some of the complexities involved with managing
  153. large sets of packages with many interdependencies. For a user who is
  154. unfamiliar with the concepts and the ways of the debian package management
  155. system, it can be quite overwhelming. Although \fBdselect\fP is aimed
  156. at easing package management and administration, it is only instrumental
  157. in doing so and can not be assumed to be a sufficient substitute for
  158. administrator skill and understanding. The user is required to
  159. be familiar with the concepts underlying the Debian packaging system.
  160. In case of doubt, consult the \fBdpkg(8)\fP manpage and the Debian
  161. policy manual.
  162. .sp
  163. Unless \fBdselect\fP is run in expert
  164. or immediate mode, a help screen is first displayed when choosing this
  165. action from the menu. The user is \fIstrongly\fP advised to study all of
  166. the information presented in the online help screens, when one pops up.
  167. The online help screens can at any time be invoked with the \fB'?'\fP key.
  168. .sp
  169. .SS Screen layout
  170. .sp
  171. The select screen is by default split in a top and a bottom half.
  172. The top half shows a list of packages. A cursor bar can select an
  173. individual package, or a group of packages, if applicable, by selecting
  174. the group header. The bottom half of the screen shows some details
  175. about the package currently selected in the top half of the screen.
  176. The type of detail that is displayed can be varied.
  177. .sp
  178. Pressing the \fB'I'\fP key toggles a full-screen display of the packages
  179. list, an enlarged view of the package details, or the equally split screen.
  180. .sp
  181. .SS Package details view
  182. .sp
  183. The package details view by default shows the extended package description
  184. for the package that is currently selected in the packages status list.
  185. The type of detail can be toggled by pressing the \fB'i'\fP key. This
  186. alternates between:
  187. - the extended description
  188. - the control information for the installed version
  189. - the control information for the available version
  190. .sp
  191. In a dependency resolution screen, there is also the possibility of
  192. viewing the specific unresolved depends or conflicts related to the
  193. package and causing it to be listed.
  194. .sh
  195. .SS Packages status list
  196. .sp
  197. The main select screen displays a list of all packages known to the debian
  198. package management system. This includes packages installed on the system
  199. and packages known from the available packages database.
  200. .sp
  201. For every package, the list shows the package's status, priority,
  202. section, installed and available versions, the package name and its
  203. short description, all in one line. By pressing the \fB'V'\fP key,
  204. the display of the installed and available version can be toggled between
  205. on an off. By pressing the \fB'v'\fP key,
  206. the package status display is toggled between verbose and shorthand.
  207. Shorthand display is the default.
  208. .sp
  209. The shorthand status indication consists
  210. of four parts: an error flag, which should normally be clear, the
  211. current status, the last selection state and the current selection state.
  212. The first two relate to the actual state of the package, the second pair
  213. are about the selections set by the user.
  214. .sp
  215. These are the meanings of the shorthand package status indicator codes:
  216. Error flag:
  217. \fIempty\fP no error
  218. \fBR\fP serious error, needs reinstallation;
  219. Installed state:
  220. \fIempty\fP not installed;
  221. \fB*\fP fully installed and configured;
  222. \fB-\fP not installed but some config files may remain;
  223. \fBU\fP unpacked but not yet configured;
  224. \fBC\fP half-configured (an error happened);
  225. \fBI\fP half-installed (an error happened).
  226. Current and requested selections:
  227. \fB*\fP marked for installation or upgrade;
  228. \fB-\fP marked for removal, configuration files remain;
  229. \fB=\fP on hold: package will not be processed at all;
  230. \fB_\fP marked for purge, also remove configuration;
  231. \fBn\fP package is new and has yet to be marked.
  232. .sp
  233. .SS Cursor and screen movement
  234. .sp
  235. The package selection list and the dependency conflict
  236. resolution screens can be navigated using motion
  237. commands mapped to the following keys:
  238. .br
  239. \fBp, Up, k\fP move cursor bar up
  240. \fBn, Down, j\fP move cursor bar down
  241. \fBP, Pgup, Backspace\fP scroll list 1 page up
  242. \fBN, Pgdn, Space\fP scroll list 1 page down
  243. \fB^p\fP scroll list 1 line up
  244. \fB^n\fP scroll list 1 line down
  245. \fBt, Home\fP jump to top of list
  246. \fBe, End\fP jump to end of list
  247. \fBu\fP scroll info 1 page up
  248. \fBd\fP scroll info 1 page down
  249. \fB^u\fP scroll info 1 line up
  250. \fB^d\fP scroll info 1 line down
  251. \fBB, Left-arrow\fP pan display 1/3 screen left
  252. \fBF, Right-arrow\fP pan display 1/3 screen right
  253. \fB^b\fP pan display 1 character left
  254. \fB^f\fP pan display 1 character right
  255. .sp
  256. .SS Searching and sorting
  257. .sp
  258. The list of packages can be searched by package name. This
  259. is done by pressing \fB'/'\fP, and typing a simple search
  260. string. The string is interpreted literally and should not contain
  261. metacharacters, like those used in ergular expressions or file globs.
  262. Repeated searching is accomplished by repeatedly pressing
  263. the \fB'n'\fP or \fB'\\'\fP keys, until the wanted package is found.
  264. If the search reaches the bottom of the list, it wraps to the top
  265. and continues searching from there.
  266. .sp
  267. The list sort order can be varied by pressing
  268. the \fB'o'\fP and \fB'O'\fP keys repeatedly.
  269. The following nine sort orderings can be selected:
  270. alphabet available status
  271. priority+section available+priority status+priority
  272. section+priority available+section status+section
  273. .br
  274. Where not listed above explicitly, alphabetic order is used as
  275. the final subordering sort key.
  276. .sp
  277. .SS Altering selections
  278. .sp
  279. The requested selection state of individual packages may be
  280. altered with the following commands:
  281. \fB+, Insert\fP install or upgrade
  282. \fB=, H\fP hold in present state and version
  283. \fB:, G\fP unhold: upgrade or leave uninstalled
  284. \fB-, Delete\fP remove, but leave configuration
  285. \fB_\fP remove & purge configuration
  286. .sp
  287. When the change request results in one or more unsatisfied depends
  288. or conflicts, \fBdselect\fP prompts the user with a dependency resolution
  289. screen. This will be further explained below.
  290. .sp
  291. It is also possible to apply these commands to groups of package
  292. selections, by pointing the cursor bar onto a group header. The
  293. exact grouping of packages is dependent on the current list ordering
  294. settings.
  295. .sp
  296. Proper care should be taken when altering large groups of selections,
  297. because this can instantaneously create large numbers of unresolved
  298. depends or conflicts, all of which will be listed in one dependency
  299. resolution screen, making them very hard to handle. In practice,
  300. only hold and unhold operations are useful when applied to groups.
  301. .sp
  302. .SS Resolving depends and conflicts
  303. .sp
  304. When the change request results in one or more unsatisfied depends
  305. or conflicts, \fBdselect\fP prompts the user with a dependency resolution
  306. screen. First however, an informative help screen is displayed.
  307. .sp
  308. The top half of this screen lists all the packages that will have
  309. unresolved depends or conflicts, as a result of the requested change,
  310. and all the packages whose installation can resolve any of these
  311. depends or whose removal can resolve any of the conflicts.
  312. The bottom half defaults to show the depends or conflicts that
  313. cause the currently selected package to be listed.
  314. .sp
  315. When the sublist of packages is displayed initially, \fBdselect\fP
  316. may have already set the requested selection status of some of the
  317. listed packages, in order to resolve the depends of conflicts that
  318. caused the dependency resolution screen to be displayed. Usually,
  319. it is best to follow up the suggestions made by \fBdselect\fP.
  320. .sp
  321. The listed packages' selection state may be reverted to the original
  322. settings, as they were before the unresolved depends or conflicts
  323. were created, by pressing the \fB'R'\fP key. By pressing the \fB'D'\fP
  324. key, the automatic suggestions are reset, but the change that caused
  325. the dependency resolution screen to be prompted is kept as requested.
  326. Finally, by pressing \fB'U'\fP, the selections are again set to the
  327. automatic suggestion values.
  328. .sp
  329. .SS Establishing the requested selections
  330. .sp
  331. By pressing \fBenter\fP, the currently displayed set of selections
  332. is accepted. If \fBdselect\fP detects no unresolved depends as a result
  333. of the requested selections, the new selections will be set. When
  334. If there are however any unresolveded depends, \fBdselect\fP will again
  335. prompt the user with a dependency resolution screen.
  336. .sp
  337. To alter a set of selections that creates unresolved depends or
  338. conflicts and forcing \fBdselect\fP to accept it, press the \fB'Q'\fP
  339. key. This sets the selections as specified by the user,
  340. unconditionally. Generally, don't do this unless you've read
  341. the fine print.
  342. .sp
  343. The opposite effect, to back out any selections change requests and
  344. go back to the previous list of selections, is attained by pressing
  345. the \fB'X'\fP or \fBescape\fP keys. By repeatedly pressing these
  346. keys, any possibly detrimental changes to the requested package
  347. selections can be backed out completely to the last established
  348. settings.
  349. .sp
  350. .SH BUGS
  351. The
  352. .B dselect
  353. package selection interface is confusing to some new users.
  354. Reportedly, it even makes seasoned kernel developers cry.
  355. .sp
  356. .B dselect
  357. doesn't handle Recommends: field very well.
  358. .sp
  359. The documentation is lacking.
  360. .sp
  361. There is no help option in the main menu.
  362. .sp
  363. The visible list of available packages cannot be reduced.
  364. .sp
  365. The built in access methods can no longer stand up to current quality
  366. standards. Use the access method provided by apt, it is not only not
  367. broken, it is also much more flexible than the built in access methods.
  368. .SH SEE ALSO
  369. .BR dpkg (8),
  370. .BR apt-get (8),
  371. .BR sources.list (5),
  372. .BR deb (5),
  373. the Debian policy manual.
  374. .SH AUTHORS
  375. .B dselect
  376. was written by Ian Jackson (ijackson@gnu.ai.mit.edu). Full list of
  377. contributors may be found in `dselect --license'.
  378. .br
  379. This manual page was written by Juho Vuori <javuori@cc.helsinki.fi>,
  380. Josip Rodin and Joost kooij.