summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--Master/texmf/doc/man/man1/tlmgr.184
-rw-r--r--Master/texmf/doc/man/man1/tlmgr.pdfbin36699 -> 38100 bytes
2 files changed, 59 insertions, 25 deletions
diff --git a/Master/texmf/doc/man/man1/tlmgr.1 b/Master/texmf/doc/man/man1/tlmgr.1
index 260e1966070..c334efec6f8 100644
--- a/Master/texmf/doc/man/man1/tlmgr.1
+++ b/Master/texmf/doc/man/man1/tlmgr.1
@@ -129,7 +129,7 @@
.\" ========================================================================
.\"
.IX Title "TLMGR 1"
-.TH TLMGR 1 "2009-08-06" "perl v5.8.8" "User Contributed Perl Documentation"
+.TH TLMGR 1 "2009-08-08" "perl v5.8.8" "User Contributed Perl Documentation"
.SH "NAME"
tlmgr \- the TeX Live Manager
.SH "SYNOPSIS"
@@ -147,8 +147,11 @@ The most up-to-date version of this documentation is available at
tlmgr itself, disaster recovery when it's broken, and test versions.
.SH "OPTIONS"
.IX Header "OPTIONS"
-The following options to \f(CW\*(C`tlmgr\*(C'\fR have to be given \fIbefore\fR you specify
-the main action to perform. In all cases, \f(CW\*(C`\-\-\*(C'\fR\fIoption\fR and
+The following options to \f(CW\*(C`tlmgr\*(C'\fR are global options not specific to
+any action. Although we present \f(CW\*(C`tlmgr\*(C'\fR invocation in the above order,
+all options can be given at any place and in arbitrary order. The first
+non-option argument will be the main action.
+In all cases, \f(CW\*(C`\-\-\*(C'\fR\fIoption\fR and
\&\f(CW\*(C`\-\*(C'\fR\fIoption\fR are equivalent, and an \f(CW\*(C`=\*(C'\fR is optional between an option
name and its value.
.IP "\fB\-\-location\fR \fIlocation\fR" 4
@@ -196,7 +199,8 @@ The standard options for TeX Live programs are also accepted:
the TeXLive::TLUtils documentation.
.PP
The \f(CW\*(C`\-\-version\*(C'\fR option shows version information about the TeX Live
-release as well as the \f(CW\*(C`tlmgr\*(C'\fR script itself.
+release as well as the \f(CW\*(C`tlmgr\*(C'\fR script itself. If paired with \f(CW\*(C`\-v\*(C'\fR,
+revision number for the used TeX Live Perl modules are shown, too.
.SH "ACTIONS"
.IX Header "ACTIONS"
.Sh "help"
@@ -249,19 +253,31 @@ at the installation source. Either \f(CW\*(C`\-\-all\*(C'\fR or at least one \f
must be specified. Options:
.IP "\fB\-\-all\fR" 4
.IX Item "--all"
-Update all installed packages except for tlmgr itself. For packages
-contained in an installed collection, also install new packages and
-remove deleted packages in those collections. Packages not contained
-in an installed collection are not considered for addition or removal.
-.Sp
-More precisely, if both the server and the local installation have a
-collection C, and C on the server contains a package A that is not
-present locally, A will be added. Conversely, if the local collection C
-contains a package B, but B is no longer in the server's C, then B will
-be deleted.
+Update all installed packages except for tlmgr itself.
.Sp
In case that updates to tlmgr itself are present this will not work
unless also the option \fB\-\-force\fR or \fB\-\-self\fR is given.
+.Sp
+Besides updating the installed packages, during the update of a
+collection the contained packages are syncronized to the status
+of the new version of the collection. That means that if a package
+has been removed on the server (and thus has also been removed from
+the respective collection), tlmgr will remove the package also on
+the local installation. This is called \fBauto-remove\fR and is announced
+as such when using the option \fB\-\-list\fR. The auto-removal can be
+suppressed using the option \fB\-\-no\-auto\-remove\fR.
+.Sp
+On the other hand, if a package has been added to an installed
+collection, it will be added to the local installation. This is called
+\&\fBauto-install\fR and is announced as such when using the option
+\&\fB\-\-list\fR. The auto-installation can be suppressed using the option
+\&\fB\-\-no\-auto\-install\fR.
+.Sp
+An exception to the collection dependency checks (including
+auto-installation of packages as mentionned above) are those that have
+been forcibly removed (see the action \fBremove\fR for details). To
+include, or better reinstall, those forcibly removed package use
+\&\fB\-\-reinstall\-forcibly\-removed\fR.
.IP "\fB\-\-self\fR" 4
.IX Item "--self"
Update tlmgr itself (that is, the infrastructure packages) if updates
@@ -284,8 +300,8 @@ written to the terminal. This is a more detailed report than \f(CW\*(C`\-\-list
Force update of packages even if updates to tlmgr itself are present.
Updates to tlmgr are not performed unless \fB\-\-self\fR option is also given.
(\f(CW\*(C`\-\-list\*(C'\fR is still performed regardless of this option.)
-.IP "\fB\-\-no\-remove\fR" 4
-.IX Item "--no-remove"
+.IP "\fB\-\-no\-auto\-remove\fR" 4
+.IX Item "--no-auto-remove"
Under normal circumstances tlmgr tries to remove packages which have
disappeared on the server when called with \f(CW\*(C`\-\-all\*(C'\fR, as described
above. This prevents any such removals.
@@ -295,17 +311,30 @@ Under normal circumstances tlmgr will install packages which are
new on the server when called with \f(CW\*(C`\-\-all\*(C'\fR. This prevents any such
automatic installation. Note that after this the packages that
would have been auto-installed will be considered as
-forcibly removed.
-.IP "\fB\-\-no\-forcibly\-removed\fR" 4
-.IX Item "--no-forcibly-removed"
-Under normal circumstances tlmgr will not install packages that
-it considers forcibly removed as described above. This option makes
-tlmgr consider all these packages as new and re-install them. This
-can be used to syncronize an installation with the server's
-idea of what is available by calling
+forcibly removed. Actually, if `foobar' is the only new package on
+server, then
.Sp
.Vb 1
-\& tlmgr update --no-forcibly-removed --all
+\& tlmgr update --all --no-auto-install
+.Ve
+.Sp
+is equivalent to
+.Sp
+.Vb 2
+\& tlmgr update --all
+\& tlmgr remove --force foobar
+.Ve
+.IP "\fB\-\-reinstall\-forcibly\-removed\fR" 4
+.IX Item "--reinstall-forcibly-removed"
+Under normal circumstances tlmgr will not install packages that it
+considers forcibly removed (that is, removed with `remove \-\-force' or
+whose installation was prohibited by \-\-no\-auto\-install during an
+earlier update). This option makes tlmgr consider all these packages
+as new and re-install them. This can be used to syncronize an
+installation with the server's idea of what is available by calling
+.Sp
+.Vb 1
+\& tlmgr update --reinstall-forcibly-removed --all
.Ve
.IP "\fB\-\-backup\fR and \fB\-\-backupdir\fR \fIdirectory\fR" 4
.IX Item "--backup and --backupdir directory"
@@ -415,6 +444,11 @@ See above under \fBaction\fR (and beware).
By default, removal of a package or collection that is a dependency of
another collection or scheme is not allowed. With this option, the
package will be removed unconditionally. Use with care.
+.Sp
+A package that has been removed using the \fB\-\-force\fR switch because
+it is still listed in an installed collection or scheme will not be
+update and mentioned as \fBforcibly removed\fR in the output of
+\&\fBtlmgr update \-\-list\fR.
.IP "\fB\-\-dry\-run\fR" 4
.IX Item "--dry-run"
Nothing is actually removed; instead, the actions to be performed are
diff --git a/Master/texmf/doc/man/man1/tlmgr.pdf b/Master/texmf/doc/man/man1/tlmgr.pdf
index 5d4137d89b1..5a8a2a37757 100644
--- a/Master/texmf/doc/man/man1/tlmgr.pdf
+++ b/Master/texmf/doc/man/man1/tlmgr.pdf
Binary files differ