summaryrefslogtreecommitdiff
path: root/Master/tlpkg/doc/packages.txt
blob: 22987b318780798a2ca9881acd77f60ee8fccbdc (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
$Id$
Public domain.

See http://tug.org/texlive/pkgupdate.html for what information there is
on the CTAN-to-TL update process.

To add a new architecture:
- check that the config.guess output maps to our architecture name
  (the `platform' routine in TeXLive/TLUtils.pm)
- create directory in Master/bin and add at least one file
- add lzma and lzmadec binaries in Master/tlpkg/installer
- add description in Master/tlpkg/TeXLive/TLUtils.pm
- regenerate tlpdb.


When switching the release version, the default network directory
specified in tl-update-tlnet, TLConfig.pm, and release-texlive-txt.
Change those.  Then make the new directory, and copy in
tlpkg/texlive.tlpdb; tl-update-tlnet will make everything else.  But
consider mv-ing the old directory so as not to actually make new
containers.  Coordinate with CTAN.


To make the tag + branch of (or to prepare for) a new release:
svn copy -r 10402 -m'texlive-2008.0 tag based on r10402' svn://tug.org/texlive/trunk svn://tug.org/texlive/tags/texlive-2008.0
svn copy -r 10402 -m'branch2008 branch based on r10402' svn://tug.org/texlive/trunk svn://tug.org/texlive/branches/branch2008

It's the same command, just different destinations.
http://svnbook.red-bean.com/en/1.5/svn-book.html#svn.branchmerge

Do both a branch and a tag so that it's possible to easily compare the
current state of the branch with its starting point (the tag).