another update to repository-setup.txt

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

1 files changed, 60 insertions, 0 deletions

diff --git a/Master/tlpkg/doc/repository-setup.txt b/Master/tlpkg/doc/repository-setup.txt
index affaec632f2..293d0f107f6 100644
--- a/Master/tlpkg/doc/repository-setup.txt
+++ b/Master/tlpkg/doc/repository-setup.txt
@@ -25,6 +25,8 @@ Contents
 4. Creating the TeX Live Database
 5. Adjusting the revision numbers
 6. Making the web distribution
+7. Testing your distribution
+8. Final notes (and not supported stuff)
 
 
 0. Preliminaries
@@ -166,7 +168,65 @@ use for doing some checks on your repository.
 
 5. Adjusting the revision numbers
 ---------------------------------
+While reading through the texlive.tlpdb you might have seen that all the 
+packages will have 
+	revision 0
+in there. The revision is used for checking which one is newer. So if you 
+have different "releases" of a package you should increase the revision
+number from one step to the next.
+
+If you want to change that, there are several options:
+- do it by hand in the texlive.tlpdb
+  that is fine, but you should remember what you have already shipped
+- do it automatically with some script which takes into account the already
+  shipped version of the packages, or the version of the package in
+  the main TeX Live repository (if you replace a TeX Live package)
+  An example for doing that take a look at our repository
+  tlpkg/etc/tlrepo-from-minimals.pl
 
 6. Making the web distribution
 ------------------------------
+Now that the texlive.tlpdb has been set up, revision numbers adjusted, you
+can create or update your web distribution with
+	perl ROOT/tlpkg/bin/tl-update-containers -location DEST -no-setup
+The -location gives the place where your former distribution was or where
+it should be created. In the former case only those containers with larger
+revision numbers are recreated. In the latter case all containers are
+created.
+
+The option -no-setup does not call the built-in routines for determining the
+location of the lzma and tar binary, and calls simply "lzma" and "tar". So
+you should have them in your PATH. If you do not give this option you also
+have to check out some more files, like config.guess, and tlpkg/installer
+where the binaries for lzma for the architectures we ship are present.
+
+7. Testing your distribution
+----------------------------
+Having complete all your steps you can test your distribution by calling
+the TeX Live Manager with the location argument. Continuing the above
+exmaple we use DEST:
+	tlmgr -location DEST update --list
+or 
+	tlmgr -location DEST update --all
+or 
+	tlmgr -location DEST list
+etc etc. Please see the documentation of tlmgr (POD again) for details.
+
+8. Final notes (and not supported stuff)
+----------------------------------------
+We cannot repeat it often enough, please don't play around with files not
+belonging to your packages. That is dangerous!
+
+Finally, not that besides the usual post installation stuff (running mktexlsr,
+fmtutil and updmap) you have no way to change the post installation 
+and removal procedure at this time. Currently all the Post actions are
+hard coded into tlpkg/TeXLive/TLPostActions.pm as it is on the installed
+system (not the one in your repo, so changing something there will NOT
+help). You might ask us for including something there (but we need GOOD
+reason for that), or you have to wait until we extended the infrastructure
+such that post actions can be specified freely in the .tlpsrc file.
+
+
+If you have further comments, questions, additions to this file please
+let us know at tex-live@tug.org.