summaryrefslogtreecommitdiff
path: root/Master/tlpkg/doc
diff options
context:
space:
mode:
authorNorbert Preining <preining@logic.at>2008-11-04 09:48:44 +0000
committerNorbert Preining <preining@logic.at>2008-11-04 09:48:44 +0000
commit2b383a0e27298adf169c718af7fccc3ef6ce3b63 (patch)
treeb45847ee9bd9900e14011bf529abf69aef1958ad /Master/tlpkg/doc
parent234325c55dee797eacec19ec5f51562c00efffa2 (diff)
add comments to the comments
git-svn-id: svn://tug.org/texlive/trunk@11178 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Master/tlpkg/doc')
-rw-r--r--Master/tlpkg/doc/multi-support.txt19
1 files changed, 19 insertions, 0 deletions
diff --git a/Master/tlpkg/doc/multi-support.txt b/Master/tlpkg/doc/multi-support.txt
index d7cfcc6e760..41d03cc15c5 100644
--- a/Master/tlpkg/doc/multi-support.txt
+++ b/Master/tlpkg/doc/multi-support.txt
@@ -15,12 +15,24 @@ examples:
done
[karl: how do these lines get added? tool, manual editing of tlpdb?]
+[norbert: tlmgr location url1 url2=tag1 url3 url4=tag2 ...
+ # sets url1, url2 with tag tag1, url3, and url4 with tag2
+ # as the list of available locations
+ # backward compatibility with former usage
+ tlmgr location add ...
+ # adds locations to the list of available locs
+ tlmgr location remove ...
+ # removes locations ...
+]
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.]
+[norbert: Why, can you explain why you don't like that the highest revision
+ number wins?]
+
That will be achieved by
tlmgr install package
@@ -48,6 +60,8 @@ or the one given via cmdline
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.]
+[norbert: agreed, that texmf-local might be a better place. should be
+ thought out]
That file contains lines
package:tag:pin
@@ -63,6 +77,10 @@ Now the evaluation *which* package will be installed will be done as follows:
[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?]
+[norbert: well, it depends. There will be a default pin value of say 500,
+ and you can give pin values lower than 500 to prefer packages from other
+ sources, or higher pin values to prefer these sources]
+
2) compute the pins of all the candidates
3) if there are different pins cancel those candidates with a non-maximal pin
@@ -85,3 +103,4 @@ Consequences of the above:
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.]
+[norbert: see above ... I don't see the wrong point ;-) ]