update repository-setup.txt according to Dohyun Kim's comments, and

add some more.


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

1 files changed, 25 insertions, 17 deletions

diff --git a/Master/tlpkg/doc/repository-setup.txt b/Master/tlpkg/doc/repository-setup.txt
index d3b5f9b005b..e55c2d1ab9b 100644
--- a/Master/tlpkg/doc/repository-setup.txt
+++ b/Master/tlpkg/doc/repository-setup.txt
@@ -5,10 +5,10 @@ How to set up your own TeX Live Packages repository
 
 (This document is public domain.)
 
-TeX Live 2008 contains the TeX Live Manager, which allows updates over
-the network. By specifying different installation sources the user can
-in theory install packages using tlmgr from a different source as the
-default TeX Live repository.
+TeX Live 2008 (and later) contains the TeX Live Manager, which allows 
+updates over the network. By specifying different installation sources
+the user can in theory install packages using tlmgr from a different
+source as the default TeX Live repository.
 
 This document describes how to set up a repository in a way that tlmgr
 can use it. Possible applications include distribution of company-internal
@@ -54,7 +54,7 @@ That means, with ROOT as the root of your local "repository":
 	ROOT/tlpkg/		infrastructure stuff, modules, scripts
 	ROOT/texmf-dist/	stuff where you should put your 
 				TeX code, fonts etc
-	ROOT/texmf{,-doc}	if you have the need for that please read
+	ROOT/texmf		if you have the need for that please read
 				first about their usage in the 
 				TeX Live Guide.
 
@@ -85,7 +85,7 @@ Put the above files into
 	ROOT/tlpkg/bin
 After that put all of YOUR files in a TDS compliant way in one of the texmf
 trees, texmf-dist, texmf, texmf-doc.
-	ROOT/texmf{,-dist,-doc}
+	ROOT/texmf{,-dist}
 We recommend putting all the files in 
 	ROOT/texmf-dist
 or, if you are replacing a package which is already present in TeX Live,
@@ -105,26 +105,27 @@ You have to have ONE .tlpsrc file for each package you want to ship, and
 furthermore ONE for your overall installation, called
 00texlive.config.tlpsrc.  This should contain (at least) the following
 lines:
-	name 00texlive.config
 	category TLCore
 	depend container_split_src_files
 	depend container_split_doc_files
-	depend container_format/lzma
-	depend release/YOUR_ID_AND_MAYBE_YEAR
+	depend container_format/xz
+	depend release/NNNN-YOUR_ID
 
 The "container_split_src_files" and "container_split_doc_files" are
 options, they specify whether at a later stage the container script will
-generate separate .tar.lzma archives for source and doc files, or put
-all of them into one .tar.lzma. It is up to you.
+generate separate .tar.xz archives for source and doc files, or put
+all of them into one .tar.xz. It is up to you.
 
 The 
-	depend container_format/lzma
+	depend container_format/xz
 is *obligatory* because currently we do NOT support any other format.
 Finally the 
-	depend release/YOUR_ID_AND_MAYBE_YEAR
-is not used, but you could add here some identification string;
-it can't hurt, and we might be able to display it to the user in the
-future.
+	depend release/NNNN-YOUR_ID
+is necessary to keep repositories tied to a release. You have to use
+for NNNN the current year. If tlmgr finds something different then
+the current release year in the first 4 characters it will refuse
+to operate. So a typical example would be
+	depend release/2009-mycompany
 
 For the rest of your package you should create .tlpsrc files describing
 their content. Either copy one of our .tlpsrc files, or (much better) 
@@ -140,7 +141,6 @@ the files in
 	ROOT/texmf-dist/source/latex/foobar/
 	ROOT/texmf-dist/doc/latex/foobar/
 then create a two-line .tlpsrc file foobar.tlpsrc containing:
-	name foobar
 	category Package
 (that is all). The rest will be automatically done by our scripts. If you
 want to understand that, read the section on auto-generated patterns in 
@@ -164,6 +164,12 @@ You can add the option
 which will warn on missing files for Windows; some of those warnings are
 by default suppressed.
 
+Another option that might be of interest is
+	-no-revision-check
+Normally if there is an old tlpdb the packages in the new one are compared
+with the packages in the old one and checked that the revisions are
+increasing.
+
 As usual, please read the documentation of tl-update-tlpdb (again in POD)
 for further information.
 
@@ -252,3 +258,5 @@ infrastructure such that post actions can be specified freely in the
 If you have further comments, questions, additions to this file please
 let us know at tex-live@tug.org.
 
+
+Last changed 2009-09-10 by np, based on comments of Dohyun Kim (kotex)