[subversion-commit] SVN tetex-base commit + diffs: r1102 - tetex-base/trunk/debian

[Frank Küster]

Author: frank
Date: 2006-03-23 13:21:57 +0000 (Thu, 23 Mar 2006)
New Revision: 1102

Added:
   tetex-base/trunk/debian/LICENSE.procedure
Log:
add a text describing usage of the tpm2licenses script

Added: tetex-base/trunk/debian/LICENSE.procedure
===================================================================
--- tetex-base/trunk/debian/LICENSE.procedure	2006-03-23 13:20:30 UTC (rev 1101)
+++ tetex-base/trunk/debian/LICENSE.procedure	2006-03-23 13:21:57 UTC (rev 1102)
@@ -0,0 +1,45 @@
+This file documents the technical aspects of the license review of
+tetex (and texlive).  The actual "legal" procedure is documented in
+debian/copyright.header. 
+
+- Prerequisites
+
+    Perl packages
+    ~~~~~~~~~~~~~
+
+  The following packages need to be installed: 
+  libconfig-general-perl, ?
+
+  libxml-dom-perl would be nice, too, but currently there's a copy in
+  "Master" in the texlive sources
+
+  Similarly, Tpm.pm from texlive's "Master" is needed.  If you have
+  libxml-dom-perl installed and put Tpm.pm in a subdirectory "Tools"
+  somewhere, passing the parent of "Tools" to the script as Master
+  *should* work.  Untested!
+
+
+    Source trees
+    ~~~~~~~~~~~~
+
+  Obviously, you need the tree(s) you want to check - that would mean
+  either tetex-base and tetex-src, or tetex-bin (in the future...), or
+  texlive. 
+
+  Furthermore, you need a local copy of the TeX Catalogue for reading
+  the license info.  Or not - you can pass --nocatalogue to the
+  script, it will then ignore the non-existence of the catalogue.
+  This is useful for verifying that the files listed in a tpm file are
+  correct, and all under the same license.  Please also try to check
+  (e.g. using the catalogue that comes with tetex-doc or the online
+  catalogue) whether a license is registered *and* verified (probably
+  that's impossible with the html version?), and anyway submit license
+  information with the corrected tpm file.
+
+- Calling the script
+
+  The packages now have a configuration file in the svn tree.  If that
+  doesn't fit your setup, you can override it with a file in your home
+  directory, or you can pass long command line options
+  (--master=some/dir to override the "Master = some/other/dir" in the
+  configuration file).