1
0
mirror of https://github.com/moparisthebest/pacman synced 2024-12-22 15:58:50 -05:00

Add information on version comparison to manpages

Signed-off-by: Dan McGee <dan@archlinux.org>
This commit is contained in:
Dan McGee 2008-06-19 19:28:56 -05:00
parent d594b6e797
commit 7edb2e5b0d
2 changed files with 9 additions and 2 deletions

View File

@ -214,7 +214,8 @@ similar to `$_basekernver`.
Force the package to be upgraded by a pacman system upgrade Force the package to be upgraded by a pacman system upgrade
operation, even if the version number would normally not trigger operation, even if the version number would normally not trigger
such an upgrade. This is useful when the version numbering scheme such an upgrade. This is useful when the version numbering scheme
of a package changes (or is alphanumeric). of a package changes (or is alphanumeric). See linkman:pacman[8] for
more infomation on version comparisons.
build() Function build() Function

View File

@ -61,7 +61,13 @@ provide the same functionality as foo will be searched for. If any package is
found, it will be installed. found, it will be installed.
+ +
You can also use `pacman -Su` to upgrade all packages that are out of date. See You can also use `pacman -Su` to upgrade all packages that are out of date. See
<<SO,Sync Options>> below. <<SO,Sync Options>> below. When upgrading, pacman performs version comparison
to determine which packages need upgrading. This behavior operates as follows:
Alphanumeric:
1.0 < 1.0a < 1.0alpha < 1.0b < 1.0beta < 1.0p < 1.0pre < 1.0rc
Numeric:
1 < 1.0 < 1.1 < 1.1.1 < 1.2 < 2.0 < 3.0.0
*-U, \--upgrade*:: *-U, \--upgrade*::
Upgrade or add a package to the system. Either a URL or file path can be Upgrade or add a package to the system. Either a URL or file path can be