FS#8021 - pacman -S unstable/package feature not documented
Attached to Project:
Pacman
Opened by Panos Papadopoulos (disharmonic) - Saturday, 15 September 2007, 08:05 GMT
Last edited by Roman Kyrylych (Romashka) - Tuesday, 25 September 2007, 09:24 GMT
Opened by Panos Papadopoulos (disharmonic) - Saturday, 15 September 2007, 08:05 GMT
Last edited by Roman Kyrylych (Romashka) - Tuesday, 25 September 2007, 09:24 GMT
|
Details
Description:
The option pacman -S unstable/package is not documented in the manpage for pacman and therefore it is not clear how someone would install a package from the unstable repository. Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: |
This task depends upon
Closed by Roman Kyrylych (Romashka)
Tuesday, 25 September 2007, 09:24 GMT
Reason for closing: Fixed
Additional comments about closing: fixed in git
Tuesday, 25 September 2007, 09:24 GMT
Reason for closing: Fixed
Additional comments about closing: fixed in git
http://www.archlinux.org/pipermail/arch-dev-public/2007-September/001617.html
Nevertheless report is valid, it just should be said that -S <repo>/<package> works (I used it sometimes for testin or my custom repo).
index 5e5d2f5..bf41ae4 100644
--- a/doc/pacman.8.txt
+++ b/doc/pacman.8.txt
@@ -56,7 +56,9 @@ Operations
Synchronize packages. Packages are installed directly from the ftp
servers, including all dependencies required to run the packages. For
example, `pacman -S qt` will download and install qt and all the
- packages it depends on. You can also use `pacman -Su` to upgrade all
+ packages it depends on. If a package name exists in more than one repo, the
+ repo can be explicitly specified to clarify the package to install:
+ `pacman -S unstable/qt`. You can also use `pacman -Su` to upgrade all
packages that are out of date. See <<SO,Sync Options>> below.
*-U, \--upgrade*::
If that seems acceptable, then I'll close the bug. If not, suggest your own working.
It's better to say about testing/qt there.