summaryrefslogtreecommitdiff
path: root/Master/texmf-dist/scripts
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2019-05-19 22:36:38 +0000
committerKarl Berry <karl@freefriends.org>2019-05-19 22:36:38 +0000
commit29d1511fec9e7508af65b3bc08b02663dff572c7 (patch)
tree29def77fe491757c28ff5d252a5e5d5958a6152a /Master/texmf-dist/scripts
parent5653ce727bbbbd072f5c4e6a2d8b16a3fb4ba86f (diff)
sync,doc
git-svn-id: svn://tug.org/texlive/trunk@51168 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/texmf-dist/scripts')
-rwxr-xr-xMaster/texmf-dist/scripts/texlive/tlmgr.pl59
1 files changed, 36 insertions, 23 deletions
diff --git a/Master/texmf-dist/scripts/texlive/tlmgr.pl b/Master/texmf-dist/scripts/texlive/tlmgr.pl
index d70b0c816dc..2b52bc1e3ce 100755
--- a/Master/texmf-dist/scripts/texlive/tlmgr.pl
+++ b/Master/texmf-dist/scripts/texlive/tlmgr.pl
@@ -8619,7 +8619,7 @@ yourself if you are using this feature and want stale symlinks removed.
=item B<repository list>
-=item B<repository list I<path|tag>>
+=item B<repository list I<path|url|tag>
=item B<repository add I<path> [I<tag>]>
@@ -8632,28 +8632,41 @@ yourself if you are using this feature and want stale symlinks removed.
This action manages the list of repositories. See L<MULTIPLE
REPOSITORIES> below for detailed explanations.
-The first form (C<list>) lists all configured repositories and the
-respective tags if set. If a path, url, or tag is given after the
-C<list> keyword, it is interpreted as source from where to
-initialize a TeX Live Database and lists the contained packages.
-This can also be an up-to-now not used repository, both locally
-and remote. If one pass in addition C<--with-platforms>, for each
-package the available platforms (if any) are listed, too.
-
-The third form (C<add>) adds a repository
-(optionally attaching a tag) to the list of repositories. The forth
-form (C<remove>) removes a repository, either by full path/url, or by
-tag. The fifth form (C<set>) sets the list of repositories to the items
-given on the command line, not keeping previous settings.
-
-The last form (C<status>) reports the verification status of the
-loaded repositories in the following format: One repository per line with
-4 fields separated with a single space: The tag (which can be the same
-as the URL), the URL, the verification code (a number), and the
-verbal description of the verification status (last field extending to
-the end of line). This format is valid under machine readable output,
-while in normal output the third field (numeric verification status)
-is not present.
+The first form, C<repository list>, lists all configured repositories
+and the respective tags if set. If a path, url, or tag is given after
+the C<list> keyword, it is interpreted as the source from which to
+initialize a TL database and lists the contained packages. This can also
+be an otherwise-unused repository, either local or remote. If the option
+C<--with-platforms> is spcified in addition, for each package the
+available platforms (if any) are also listed.
+
+The form C<repository add> adds a repository (optionally attaching a
+tag) to the list of repositories, while C<repository remove> removes a
+repository, either by full path/url, or by tag.
+
+The form C<repository set> sets the list of available repositories to
+the items given on the command line, overwriting previous settings.
+
+The form C<repository status> reports the verification status of the
+loaded repositories with the format of one repository per line
+with fields separated by a single space:
+
+=over 4
+
+=item The tag (which can be the same as the url);
+
+= the url;
+
+= iff machine-readable output is specified, the verification code (a
+number);
+
+= a textual description of the verification status, as the last field
+extending to the end of line.
+
+=back
+
+That is, in normal (not machine-readable) output, the third field
+(numeric verification status) is not present.
In all cases, one of the repositories must be tagged as C<main>;
otherwise, all operations will fail!