comments

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

1 files changed, 13 insertions, 3 deletions

diff --git a/Master/tlpkg/doc/multi-support.txt b/Master/tlpkg/doc/multi-support.txt
index d261fb19b77..d7cfcc6e760 100644
--- a/Master/tlpkg/doc/multi-support.txt
+++ b/Master/tlpkg/doc/multi-support.txt
@@ -1,9 +1,9 @@
-
 Multi source support in TeX Live
 --------------------------------
 (Work in progress)
 
 (completely independent from generalized revisions)
+[karl: good.]
 
 1) extension of the location part in 00texlive-installation.config
 ------------------------------------------------------------------
@@ -14,11 +14,13 @@ examples:
 	depend location:http://server.local.uni/texlive/packages department
 
 done
+[karl: how do these lines get added? tool, manual editing of tlpdb?]
 
 2) invocation of tlmgr/installation
 -----------------------------------
 
 Normally tlmgr will install the candidate with the highest revision number.
+[karl: ok, given pinning below. otherwise i don't like it.]
 That will be achieved by
 	tlmgr install package
 
@@ -31,6 +33,7 @@ So continuing the above example we could call
 or
 	tlmgr install package/http://server.local.uni/texlive/packages
 (maybe we don't allow the later form ...?)
+[karl: well, if it's done, then I see no reason not to support it.]
 
 done
 
@@ -41,10 +44,15 @@ tlmgr will evaluate an additional config file
 	ROOT/tlpkg/pinning
 or the one given via cmdline
 	tlmgr -pins /path/to/pinning/file
+[karl: maybe it should be found in texmf-local/tlpkg? look there
+ before ROOT/tlpkg but allow both? maybe other places too. have to think
+ about it.  Also, the filename should be something clearer, perhaps
+ tlpkgpins.txt.]
 
 That file contains lines
 	package:tag:pin
 where package is a package name or * (or regexp? or glob context* eg?)
+[glob is better than regexp in this case I think]
 and tag is [a-z0-9,]+ as for tags above, or *,
 and pin is an integer between 0 and 1000.
 
@@ -52,6 +60,8 @@ Now the evaluation *which* package will be installed will be done as follows:
 
 1) create the list of candidates, i.e., all tlpobj from different sources
    where the name matches the one to be installed
+[karl: if a package is pinned to a single source (99% case, seems to
+ me), the other sources (e.g., default ctan) won't even be considered, right?]
 
 2) compute the pins of all the candidates
 
@@ -73,5 +83,5 @@ Consequences of the above:
 - default installations continue as before
 - normal installations with multiple sources but without pinning will
   simply *do*the*right*thing*, namely install the highest revision number.
-
-
+[karl: it's unclear to me that that is the right thing, in general, but
+ I can see how it is the right thing in some cases, e.g., yours, so fine.]