summaryrefslogtreecommitdiff
path: root/Build
diff options
context:
space:
mode:
authorPeter Breitenlohner <peb@mppmu.mpg.de>2011-11-08 10:04:18 +0000
committerPeter Breitenlohner <peb@mppmu.mpg.de>2011-11-08 10:04:18 +0000
commit50185f7a8763b8a19df29c26dce186b3f1a9ef09 (patch)
treee4f3db4bce619655dabaf58849d8b9ffa0d09964 /Build
parent05c3afdaa6bfbc9127d8d5e19093e6fc3281078c (diff)
Typos
git-svn-id: svn://tug.org/texlive/trunk@24544 c570f23f-e606-0410-a88d-b1316a301751
Diffstat (limited to 'Build')
-rw-r--r--Build/source/README.distro23
1 files changed, 12 insertions, 11 deletions
diff --git a/Build/source/README.distro b/Build/source/README.distro
index 0a3fb25c263..d1aaf7b796c 100644
--- a/Build/source/README.distro
+++ b/Build/source/README.distro
@@ -82,13 +82,14 @@ For a `staged install' (see Automake manual 12.4), e.g.,
all installation paths are prefixed by the value of DESTDIR.
-2. PACKAGING FOR A DISTRO
+2. Packaging for a distro
=========================
-(np, 2011-11-04, email to tldistro)
-(this describes Debian packaging, but the basic ideas are the
-same for all distros)
+From Norbert Preining <preining@logic.at>, 2011-11-04, email to tldistro.
-Let us the few important things in turn:
+This describes Debian packaging, but the basic ideas are the same for all
+distros.
+
+Let us discuss the few important things in turn:
- ls-R files
- updmap-sys/updmap.cfg
- fmtutil-sys/fmtutil.cnf
@@ -102,22 +103,22 @@ But if you want to allow for smooth upgrades etc, and partial installs,
you cannot do that.
So the Debian way for these files is:
-- at package build time we knoe which formats/font maps/hypehn patterns
- there are, and create snippets for these configuration file, and
+- at package build time we know which formats/font maps/hyphen patterns
+ there are, and create snippets for these configuration files, and
at install time put them into /etc/texmf/updmap.d, fmtutil.d, hyphen.d
- after the package has been installed the configuration routine does:
. assemble the pieces together to updmap.cfg/fmtutil.cnf/language.*
. run the necessary commands (also determined at package *build* time,
that is updmap-sys, fmtutil --whatever, etc)
Furthermore, in Debian there is another requirement, namely that
-if a sysadm changes confiurations files (hereafter called conffiles)
+if a sysadm changes configuration files (hereafter called conffiles)
in /etc, and the package is only removed (that is, the conffiles are
*NOT* deleted) but NOT purged (purged = also conffiles removed),
then a later installation of the package has to honor the changes the
sysadm made.
That means, there will remain snippets in /etc/updmap.d (for example)
-if a font package has been removed, but not purged. THese snippets
+if a font package has been removed, but not purged. These snippets
should of course NOT be merged into the main config file. So we ship
in addition a file /var/lib/texmf/fmt.d/.... and check at assemble
time if this file is present. If it is present, then the snippet
@@ -126,11 +127,11 @@ is used, if not, then it is NOT used.
about packaging, think about that, too).
Well, that is the story at least till 2007. In later version of the Debian
-packages we are now something called "triggers", where a central package
+packages we now use something called "triggers", where a central package
(in our case "tex-common") shows interest in a certain directory, namely
the directories /etc/texmf/fmtutil.d etc (all of them), and if a file
is dropped there or changed there, only some specific code in tex-common
-is executed. THis way we can reduce the calls to mktexlsr and updmap-sys
+is executed. This way we can reduce the calls to mktexlsr and updmap-sys
a *LOT* (think about installing every collection of TeX Live, and run
mktexlsr, fmtutil-sys --all, updmap-sys after *EACH* collection, versus
running it only once or twice!). But this is Debian specific, and probably