diff options
| -rw-r--r-- | Master/tlpkg/doc/multi-support.txt | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/Master/tlpkg/doc/multi-support.txt b/Master/tlpkg/doc/multi-support.txt index 41d03cc15c5..e0b3af6f3aa 100644 --- a/Master/tlpkg/doc/multi-support.txt +++ b/Master/tlpkg/doc/multi-support.txt @@ -24,6 +24,9 @@ done tlmgr location remove ... # removes locations ... ] +[k2: well, there is no "location" action now, so compatibility isn't an issue. +having this new action seems like a good idea. tlmgr option location foo +will just become a synonm for tlmgr location add foo. yes?] 2) invocation of tlmgr/installation ----------------------------------- @@ -32,6 +35,15 @@ 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?] +[k2: because it is random, except in the one case where you want to use + it. that is, i understand that you want to copy a tl package, make + some local fixes, and install it locally, keeping track of the rev + number. that's fine for you. but there's no way most people are + going to bother with that. if mojca sets up a context repo, say, + those revision numbers are (should be) completely independent of tl's + revision numbers. therefore, all the context packages should be + pinned to the context repo, so the context repo always wins. without + pinning, it would be an unmaintainable situation.] That will be achieved by tlmgr install package @@ -81,6 +93,15 @@ Now the evaluation *which* package will be installed will be done as follows: and you can give pin values lower than 500 to prefer packages from other sources, or higher pin values to prefer these sources] +[k2: I understand there is all this flexibility, but that's not my +point. I envision the single most common use of this (by far) to say +"get package foo from my special location bar", where foo is a local +font, or tlmgr from tlcritical. In these cases, the user will set a +single location. And then it would be a waste of time for tlmgr to even +consider looking at the default location (tlnet) for foo. It should not +even be a candidate.] + + 2) compute the pins of all the candidates 3) if there are different pins cancel those candidates with a non-maximal pin |