dselect.1 19 KB

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