summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/scripts
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2017-05-13 23:31:11 +0000
committerKarl Berry <karl@freefriends.org>2017-05-13 23:31:11 +0000
commitbf12109729c6dd16cad8b7310c0a1354b8315b60 (patch)
treec7352193c6a0d1bb93e0bc16d48ba95d9ab00409 /Master/texmf-dist/scripts
parentdd64b2da8b67c42251d02ce422da9cb4643043e1 (diff)
doc, test
git-svn-id: svn://tug.org/texlive/trunk@44325 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/scripts')
-rw-r--r--Master/texmf-dist/scripts/texlive/Makefile12
-rw-r--r--Master/texmf-dist/scripts/texlive/NEWS8
-rwxr-xr-xMaster/texmf-dist/scripts/texlive/tlmgr.pl91
3 files changed, 72 insertions, 39 deletions
diff --git a/Master/texmf-dist/scripts/texlive/Makefile b/Master/texmf-dist/scripts/texlive/Makefile
new file mode 100644
index 00000000000..c784104cc0b
--- /dev/null
+++ b/Master/texmf-dist/scripts/texlive/Makefile
@@ -0,0 +1,12 @@
+# $Id$
+# Public domain.
+
+test_tlmgr_html = /tmp/tlmgr.html
+live_tlmgr_html = /home/httpd/html/texlive/doc/tlmgr.html
+
+test-html:
+ pod2html --cachedir=/tmp tlmgr.pl >$(test_tlmgr_html)
+ diff $(live_tlmgr_html) $(test_tlmgr_html)
+
+install-html:
+ mv $(test_tlmgr_html) $(live_tlmgr_html)
diff --git a/Master/texmf-dist/scripts/texlive/NEWS b/Master/texmf-dist/scripts/texlive/NEWS
index 509e710d028..0af4545690f 100644
--- a/Master/texmf-dist/scripts/texlive/NEWS
+++ b/Master/texmf-dist/scripts/texlive/NEWS
@@ -1,6 +1,14 @@
(This file public domain. Originally written by Norbert Preining and
Karl Berry, 2010.)
+<p><b>tlmgr (TeX Live 2017):</b>
+<li>new action <tt>shell</tt> for interactive and scripted use.
+<li>new action <tt>conf auxtrees</tt> to easily add and remove extra
+ texmf trees.
+<li>if backups are enabled, a backup is automatically made by the
+ <tt>remove</tt> action.
+<li>the <tt>info</tt> output includes sizes for schemes and collections.
+
<p><b>tlmgr 41476 (released 20jun16):</b>
<li>fix <tt>tlmgr restore</tt> failure
diff --git a/Master/texmf-dist/scripts/texlive/tlmgr.pl b/Master/texmf-dist/scripts/texlive/tlmgr.pl
index 5d6e3448ac0..9599db1b48a 100755
--- a/Master/texmf-dist/scripts/texlive/tlmgr.pl
+++ b/Master/texmf-dist/scripts/texlive/tlmgr.pl
@@ -2472,7 +2472,7 @@ sub auto_remove_install_force_packages {
}
#
# now take only the subset of packages that is in @todo
- # note that @todo is already expanded in action_updated according
+ # note that @todo is already expanded in action_update according
# to the --no-depends and --no-depends-at-all options
#
my %removals;
@@ -7381,9 +7381,12 @@ category, short and long description, sizes, installation status, and TeX Live
revision number. If I<pkg> is not locally installed, searches in the
remote installation source.
-For normal packages (not collections or schemes), the sizes of the
-four groups of files (run/src/doc/bin files) are shown. For collections
-and schemes the B<accumulated> size including depending packages.
+For normal packages (not collections or schemes), the sizes of the four
+groups of files (run/src/doc/bin files) are shown separately. For
+collections, the cumulative size is shown, including all
+directly-dependent packages (but not dependent collections). For
+schemes, the cumulative size is also shown, including all
+directly-dependent collections and packages.
If I<pkg> is not found locally or remotely, the search action is used
and lists matching packages and files.
@@ -7577,7 +7580,8 @@ Its value is an integer. If the C<autobackup> value is C<-1>, no
backups are removed. If C<autobackup> is 0 or more, it specifies the
number of backups to keep. Thus, backups are disabled if the value is
0. In the C<--clean> mode of the C<backup> action this option also
-specifies the number to be kept.
+specifies the number to be kept. The default value is 1, so that
+backups are made, but only one backup is kept.
To setup C<autobackup> to C<-1> on the command line, use:
@@ -7591,13 +7595,14 @@ The C<sys_bin>, C<sys_man>, and C<sys_info> options are used on
Unix-like systems to control the generation of links for executables,
info files and man pages. See the C<path> action for details.
-The last three options control behavior on Windows installations. If
-C<desktop_integration> is set, then some packages will install items in
-a sub-folder of the Start menu for C<tlmgr gui>, documentation, etc. If
-C<fileassocs> is set, Windows file associations are made (see also the
-C<postaction> action). Finally, if C<multiuser> is set, then adaptions
-to the registry and the menus are done for all users on the system
-instead of only the current user. All three options are on by default.
+The last three options also affect behavior on Windows installations.
+If C<desktop_integration> is set, then some packages will install items
+in a sub-folder of the Start menu for C<tlmgr gui>, documentation, etc.
+If C<fileassocs> is set, Windows file associations are made (see also
+the C<postaction> action). Finally, if C<multiuser> is set, then
+adaptions to the registry and the menus are done for all users on the
+system instead of only the current user. All three options are on by
+default.
=head2 paper
@@ -7764,20 +7769,27 @@ package, dependencies are never removed. Options:
=over 4
-=item B<--backup> and B<--backupdir> I<directory>
+=item B<--backup>
-These two options control the creation of backups of packages I<before>
-removal; that is, backup of packages as currently installed. If
-neither of these options are given, no backup package will be saved. If
-C<--backupdir> is given and specifies a writable directory then a backup
-will be made in that location. If only C<--backup> is given, then a
-backup will be made to the directory previously set via the C<option>
-action (see below). If both are given then a backup will be made to the
-specified I<directory>.
-
-You can set options via the C<option> action to automatically create
-backups for all packages, and/or keep only a certain number of
-backups. Please see the C<option> action for details.
+=item B<--backupdir> I<directory>
+
+These options behave just as with the L</update> action (q.v.), except
+they apply to making backups of packages before they are removed. The
+default is to make such a backup, that is, to save a copy of packages
+before removal.
+
+See L</update> action for more.
+
+neither option is given, no backup will be made. If C<--backupdir> is
+given and specifies a writable directory then a backup will be made in
+that location. If only C<--backup> is given, then a backup will be made
+to the directory previously set via the C<option> action (see below). If
+both are given then a backup will be made to the specified I<directory>.
+
+You can set options via the C<option> action to automatically make
+backups for all packages, and/or keep only a certain number of backups.
+Please see the C<option> action for details. The default is to make one
+backup.
The C<restore> action explains how to restore from a backup.
@@ -8130,28 +8142,29 @@ installation with the server's idea of what is available:
tlmgr update --reinstall-forcibly-removed --all
-=item B<--backup> and B<--backupdir> I<directory>
+=item B<--backup>
+
+=item B<--backupdir> I<directory>
These two options control the creation of backups of packages I<before>
updating; that is, backup of packages as currently installed. If
-neither of these options are given, no backup package will be saved. If
-C<--backupdir> is given and specifies a writable directory then a backup
-will be made in that location. If only C<--backup> is given, then a
-backup will be made to the directory previously set via the C<option>
-action (see below). If both are given then a backup will be made to the
-specified I<directory>.
+neither options is given, no backup will made saved. If C<--backupdir>
+is given and specifies a writable directory then a backup will be made
+in that location. If only C<--backup> is given, then a backup will be
+made to the directory previously set via the L</option> action (see
+below). If both are given then a backup will be made to the specified
+I<directory>.
-You can set options via the C<option> action to automatically create
-backups for all packages, and/or keep only a certain number of
-backups. Please see the C<option> action for details.
+You can also set options via the C</option> action to automatically make
+backups for all packages, and/or keep only a certain number of backups.
C<tlmgr> always makes a temporary backup when updating packages, in case
of download or other failure during an update. In contrast, the purpose
-of this C<--backup> option is to allow you to save a persistent backup
-in case the actual I<content> of the update causes problems, e.g.,
-introduces an incompatibility.
+of this C<--backup> option is to save a persistent backup in case the
+actual I<content> of the update causes problems, e.g., introduces an TeX
+incompatibility.
-The C<restore> action explains how to restore from a backup.
+The L</restore> action explains how to restore from a backup.
=item B<--no-depends>