dselect.8 18 KB

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