summaryrefslogtreecommitdiff
path: root/Master/texmf
diff options
context:
space:
mode:
authorManuel Pégourié-Gonnard <mpg@elzevir.fr>2009-08-08 00:13:41 +0000
committerManuel Pégourié-Gonnard <mpg@elzevir.fr>2009-08-08 00:13:41 +0000
commitfb3c5fa41206e1fbd996f53a61605faa6208e0c7 (patch)
treefc990cf604c0849de343c12aa9a59d0d67a095f1 /Master/texmf
parent7fe45a369eac949694fa25632920efd3b107e813 (diff)
A few corrections/improvements to the doc about forbibly removed etc.
git-svn-id: svn://tug.org/texlive/trunk@14573 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf')
-rwxr-xr-xMaster/texmf/scripts/texlive/tlmgr.pl47
1 files changed, 29 insertions, 18 deletions
diff --git a/Master/texmf/scripts/texlive/tlmgr.pl b/Master/texmf/scripts/texlive/tlmgr.pl
index 315cbbc3209..3333f0b3651 100755
--- a/Master/texmf/scripts/texlive/tlmgr.pl
+++ b/Master/texmf/scripts/texlive/tlmgr.pl
@@ -3699,8 +3699,11 @@ must be specified. Options:
Update all installed packages except for tlmgr itself.
-Besides updating the installed packages. During the update of a
-collection the containing packages are syncronized to the status
+In case that updates to tlmgr itself are present this will not work
+unless also the option B<--force> or B<--self> is given.
+
+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
@@ -3708,19 +3711,18 @@ the local installation. This is called B<auto-remove> and is announced
as such when using the option B<--list>. The auto-removal can be
suppressed using the option B<--no-auto-remove>.
-On the other hand, if a package has been added to a collection, it
-will be added to the local installation. This is called B<auto-install>
-and is announced as such when using the option B<--list>. The
-auto-installation can be suppressed using the option B<--no-auto-install>.
+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
+B<auto-install> and is announced as such when using the option
+B<--list>. The auto-installation can be suppressed using the option
+B<--no-auto-install>.
-An exception to the auto-installation of packages are those that have been
-forcibly removed (see the action B<remove> for details). To include, or
-better reinstall, those forcibly removed package use
+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 B<remove> for details). To
+include, or better reinstall, those forcibly removed package use
B<--reinstall-forcibly-removed>.
-In case that updates to tlmgr itself are present this will not work
-unless also the option B<--force> or B<--self> is given.
-
=item B<--self>
Update tlmgr itself (that is, the infrastructure packages) if updates
@@ -3759,15 +3761,24 @@ Under normal circumstances tlmgr will install packages which are
new on the server when called with C<--all>. This prevents any such
automatic installation. Note that after this the packages that
would have been auto-installed will be considered as
-forcibly removed.
+forcibly removed. Actually, if `foobar' is the only new package on
+server, then
+
+ tlmgr update --all --no-auto-install
+
+is equivalent to
+
+ tlmgr update --all
+ tlmgr remove --force foobar
=item B<--reinstall-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
+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
tlmgr update --reinstall-forcibly-removed --all