update the man page of TLPSRC

git-svn-id: svn://tug.org/texlive/trunk@9796 c570f23f-e606-0410-a88d-b1316a301751

1 files changed, 57 insertions, 25 deletions

diff --git a/Master/tlpkg/man/TeXLive-TLPSRC.1 b/Master/tlpkg/man/TeXLive-TLPSRC.1
index 5c4761fad9f..89081e29894 100644
--- a/Master/tlpkg/man/TeXLive-TLPSRC.1
+++ b/Master/tlpkg/man/TeXLive-TLPSRC.1
@@ -1,4 +1,4 @@
-.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.05)
+.\" Automatically generated by Pod::Man 2.16 (Pod::Simple 3.07)
 .\"
 .\" Standard preamble:
 .\" ========================================================================
@@ -131,8 +131,8 @@
 .rm #[ #] #H #V #F C
 .\" ========================================================================
 .\"
-.IX Title "TeXLive::TLPSRC 3"
-.TH TeXLive::TLPSRC 3 "2008-06-09" "perl v5.10.0" "User Contributed Perl Documentation"
+.IX Title "TLPSRC 3"
+.TH TLPSRC 3 "2008-07-26" "perl v5.10.0" "User Contributed Perl Documentation"
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
@@ -246,12 +246,13 @@ enables the font map file \fIfont\fR\f(CW\*(C`.map\*(C'\fR in the \f(CW\*(C`updm
 .IX Item "execute addMixedMap font.map"
 enables the font map file \fIfont\fR\f(CW\*(C`.map\*(C'\fR for Mixed mode in the
 \&\f(CW\*(C`updmap.cfg\*(C'\fR file.
-.ie n .IP """execute BuildLanguageDat NN""" 6
-.el .IP "\f(CWexecute BuildLanguageDat NN\fR" 6
-.IX Item "execute BuildLanguageDat NN"
-activates all the hyphenation patterns found in 
-\&\f(CW\*(C`Master/texmf/tex/generic/config/language.NN.dat\*(C'\fR in the generated
-\&\f(CW\*(C`language.dat\*(C'\fR file.
+.ie n .IP """execute AddHyphen name=TEXLANG file=FILE [other vars]""" 6
+.el .IP "\f(CWexecute AddHyphen name=TEXLANG file=FILE [other vars]\fR" 6
+.IX Item "execute AddHyphen name=TEXLANG file=FILE [other vars]"
+activates the hyphenation pattern with name \s-1TEXLANG\s0 and load the file \s-1FILE\s0
+for that language. More variables can be given, currently: \fBlefthyphenmin\fR,
+\&\fBrighthyphenmin\fR (both integers), and \fBsynonyms\fR (a list of alias names
+for that hyphenation).
 .ie n .IP """execute BuildFormat FMTCFG""" 6
 .el .IP "\f(CWexecute BuildFormat FMTCFG\fR" 6
 .IX Item "execute BuildFormat FMTCFG"
@@ -270,7 +271,7 @@ Patterns specify which files are to be included into a \f(CW\*(C`tlpobj\*(C'\fR
 expansion time. Patterns are of the form
 .PP
 .Vb 1
-\&  [PREFIX]TYPE[/ARCH] PAT
+\&  [PREFIX]TYPE[/[!]ARCHSPEC] PAT
 .Ve
 .PP
 where
@@ -278,10 +279,10 @@ where
 .Vb 3
 \&  PREFIX = + | +! | !
 \&  TYPE = t | f | d | r
-\&  ARCH = <some arch specificatin>
+\&  ARCHSPEC = <list of architectures separated by comma>
 .Ve
 .PP
-Simple patterns without \s-1PREFIX\s0 and \s-1ARCH\s0 specification are explained first,
+Simple patterns without \s-1PREFIX\s0 and \s-1ARCHSPEC\s0 specification are explained first,
 see below for these extensions.
 .ie n .IP """f ""\fR\fIpath" 4
 .el .IP "\f(CWf \fR\fIpath\fR" 4
@@ -330,13 +331,26 @@ If the \f(CW\*(C`PREFIX\*(C'\fR contains the symbol \f(CW\*(C`!\*(C'\fR the mean
 reversed, i.e., file matching this pattern are removed from the list
 of included files.
 .Sp
-The prefix \f(CW\*(C`+\*(C'\fR deals with the autogeneration of patterns.
+The prefix \f(CW\*(C`+\*(C'\fR means to append to the list of automatically synthesized
+patterns, instead of replacing them.
+.Sp
+The \f(CW\*(C`+\*(C'\fR and \f(CW\*(C`!\*(C'\fR prefixes can be combined.  This is useful to exclude
+directories from the automatic pattern list.  For example,
+\&\f(CW\*(C`graphics.tlpsrc\*(C'\fR contains this line:
+.Sp
+.Vb 1
+\&  docpattern +!d texmf\-dist/doc/latex/tufte\-latex/graphics
+.Ve
+.Sp
+so that this subdirectory of the \f(CW\*(C`tufte\-latex\*(C'\fR package that happens to
+be named `graphics' is not mistakenly included in the \f(CW\*(C`graphics\*(C'\fR
+package.
 .IP "Auto generated patterns" 6
 .IX Item "Auto generated patterns"
-In the case that one of the pattern sections is empty or \fBall\fR the provided
-patterns have the prefix \f(CW\*(C`+\*(C'\fR (e.g., \f(CW\*(C`+f ...\*(C'\fR), then the following patterns
-are \fBautomatically\fR added at expansion time (but never written to the
-textual representation):
+If a given pattern section is empty or \fBall\fR the provided patterns have
+the prefix \f(CW\*(C`+\*(C'\fR (e.g., \f(CW\*(C`+f ...\*(C'\fR), then the following patterns, listed
+by type are \fIautomatically\fR added at expansion time (but never written
+to the textual representation):
 .RS 6
 .ie n .IP """runpattern""" 6
 .el .IP "\f(CWrunpattern\fR" 6
@@ -399,9 +413,9 @@ automatically expanded to the respective architecture.
 .ie n .IP """bat/exe/dll/texlua"" for win32" 6
 .el .IP "\f(CWbat/exe/dll/texlua\fR for win32" 6
 .IX Item "bat/exe/dll/texlua for win32"
-For \f(CW\*(C`binpattern\*(C'\fRs of the form \f(CW\*(C`f bin/win32/foobar\*(C'\fR (i.e., also for a
-binpattern of the form \f(CW\*(C`f bin/${ARCH}/foobar\*(C'\fR) files \f(CW\*(C`foobar.bat\*(C'\fR,
-\&\f(CW\*(C`foobar.dll\*(C'\fR, \f(CW\*(C`foobar.exe\*(C'\fR, and \f(CW\*(C`foobar.texlua\*(C'\fR are also matched.
+\&\f(CW\*(C`binpattern\*(C'\fRs of the form \f(CW\*(C`f bin/win32/foobar\*(C'\fR or
+\&\f(CW\*(C`f bin/${ARCH}/foobar\*(C'\fR) also match the files \f(CW\*(C`foobar.bat\*(C'\fR,
+\&\f(CW\*(C`foobar.cmd\*(C'\fR, \f(CW\*(C`foobar.dll\*(C'\fR, \f(CW\*(C`foobar.exe\*(C'\fR, and \f(CW\*(C`foobar.texlua\*(C'\fR.
 .Sp
 The above two properties allows to capture the binaries for all
 architectures in one binpattern
@@ -414,18 +428,36 @@ and would get \f(CW\*(C`bin/win32/dvips.exe\*(C'\fR into the runfiles for \f(CW\
 .Sp
 Note that the \f(CW\*(C`bat\*(C'\fR/\f(CW\*(C`exe\*(C'\fR expansion \fBonly\fR works for patterns of
 the \f(CW\*(C`f\*(C'\fR type!
-.IP "\s-1ARCH\s0 specification of a pattern" 6
-.IX Item "ARCH specification of a pattern"
+.IP "\s-1ARCHSPEC\s0 specification of a pattern" 6
+.IX Item "ARCHSPEC specification of a pattern"
 Sometimes some files should be included into the list of binfiles of
-a package only for one architecture. This can be done by specifying 
-the architecture after the pattern specifier using a \f(CW\*(C`/\*(C'\fR:
+a package only for some architectures, or for all but some architectures. 
+This can be done by specifying the list of architectures for which this 
+pattern should be matched after the pattern specifier using a \f(CW\*(C`/\*(C'\fR:
 .Sp
 .Vb 1
 \&  binpattern f/win32 tlpkg/bin/perl.exe
 .Ve
 .Sp
 will include the file \f(CW\*(C`tlpkg/bin/perl.exe\*(C'\fR only in the binfiles for
-the architecture win32.
+the architecture win32. Another example
+.Sp
+.Vb 1
+\&  binpattern f/arch1,arch2,arch3 path/$ARCH/foo/bar
+.Ve
+.Sp
+will only try to match this pattern for arch1, arch2, and arch3.
+.Sp
+Normally, a binpattern is matched against all possible architectures. If you
+want to exclude some architectures, instead of listing all the ones you want
+to include as above, you can prefix the list of architectures with a ! and
+these architectures will not be tested. Example:
+.Sp
+.Vb 1
+\&  binpattern f/!arch1,arch2,arch3 path/$ARCH/foo/bar
+.Ve
+.Sp
+will be matched against all architectures \fIbut\fR arch1, arch2, and arch3.
 .RE
 .RS 6
 .RE