update some docs

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

2 files changed, 40 insertions, 68 deletions

diff --git a/Master/tlpkg/etc/installed_avail_archs.diff b/Master/tlpkg/etc/installed_avail_archs.diff
index 3b3c81fc249..6c2b8c4ff8d 100644
--- a/Master/tlpkg/etc/installed_avail_archs.diff
+++ b/Master/tlpkg/etc/installed_avail_archs.diff
@@ -1,6 +1,37 @@
+Rational
+--------
+(but note that I believe it is outdated, see below)
+
+  currently there is a mess-up wrt to available and installed architectures.
+  We use 00texlive-installation/available_architectures for both the set
+  of installed archs and the set of available archs.
+  That should be better done as follows:
+  00texlive.config:
+        should contain the available_architectures stuff
+  00texlive-installation.config:
+        should contain *instead* installed_architectures stuff
+  and tlmgr should check:
+    localtlpdb/00texlive-installation.config/installed_architectures
+  for what archs are actually installed, and
+    remotetlpdb/00texlive.config/available_architectures
+  for what can be installed.
+
+  In the texlive-svn both variables would be initialized to the same thing,
+  while others that don't want to be necessary also runable as is (some
+  third party distribution of modules) should only need to set
+    00texlive.config/available_architectures
+
+
 There is some code missing that transfers the one option into the other
 in the case that the other is absent.
 
+I am more and more convinced that this patch should not be included. Because
+we will always have that
+	available_archs == installed_archs
+so that is a bit a strange thing to duplicate it. If we want to use an
+installed system as installation source it makes sense to use the
+available as it is done for now.
+
 
 Index: install-tl
 ===================================================================
diff --git a/TODO b/TODO
index ce76f1f9640..0ae551990d8 100644
--- a/TODO
+++ b/TODO
@@ -124,81 +124,22 @@ longer needed at all?
   Also not checked is that unpacking the container does not overwrite
   files from a different package.
 
+- use Net::ftp/http and keep connection open during download so not to 
+  open a new connection for all the time...
+
 - extend revisions (Master/tlpkg/etc/generalize-revisions.diff)
-  we want: [source:]NNN[.RRR]
-  - source specification for listening the origin
+  (implemented and working)
+  we want: NNN[.RRR]
   - NNN as normal revision number
   - .RRR to provide various upgrades (think of context providing
     packages with everyday addint +1 to the revision number they could
     easily overtake upstream texlive)
-  Question: Do we need the source part at all? Isn't it irrelevant?
-
-  Maybe first we go WITHOUT the source: part until we know how it will
-  be handled. THere is the option to set the source in some different way
-  via some configuration tlpdb.
-
-  See below that we don't need the whole source part at all ...
-
-- multi-source support
-  I think all that ideas with pinning etc are overkill, since we will not
-  have that many different sources. I propose that we use only revision
-  numbers
-  	NNNN[.RRRR]
-  (without any source specification) and that just the highest package
-  number will be installed.
-
-  To be done:
-  . add support for more than one 
-  	depend location:....
-    lines in the tlpdb
-  . add code to the tlmgr to load all tlpdb from all locations
-  . install just simply the hightest number
-
-  (needs generalize revision patch)
-
-  Current ideas:
-  - in the tlpdb add some short name to a source
-  	depend location:http://mirror.ctan.org/.... ctan
-	depend location:http://local.server.foo/...  department
-    and then call
-    	tlmgr install package/ctan (installs from ctan source)
-	tlmgr install package/department (installs from department)
-	tlmgr install package (installs the highest rev number)
- 
-  - add a config file
-  	package:source:pin
-    default pin is 100, higher is stronger ..
-    if "package" should be installed or upgraded, the following check is done
-    . take a look at all candidates and compute the pins of them 
-      (default is 100)
-    . promote those with the highest pin (can be only one, or all) to the
-      new set of candidates
-    . within the new set of candidates choose the highest revision number
-
-  That would allow:
-  . packages can be pinned to a specific source, and will not be updated
-    even if another source ships a higher version number
-  . ???
+
+- multi source
+	see tlpkg/doc/multi-support.txt
 
 - (Master/tlpkg/etc/installed_avail_archs.diff)
-  currently there is a mess-up wrt to available and installed architectures.
-  We use 00texlive-installation/available_architectures for both the set
-  of installed archs and the set of available archs.
-  That should be better done as follows:
-  00texlive.config:
-	should contain the available_architectures stuff
-  00texlive-installation.config:
-	should contain *instead* installed_architectures stuff
-  and tlmgr should check:
-    localtlpdb/00texlive-installation.config/installed_architectures
-  for what archs are actually installed, and 
-    remotetlpdb/00texlive.config/available_architectures 
-  for what can be installed.
-
-  In the texlive-svn both variables would be initialized to the same thing,
-  while others that don't want to be necessary also runable as is (some
-  third party distribution of modules) should only need to set
-    00texlive.config/available_architectures
+  for rational see the patch, but it should not be used.
 
 - rewrite the installer to use TLMedia instead of the horrible hacks of
   TLUtils.