Package: python2.5
Version: 2.5.1-5
Couple of documentation problems here, and a patch to fix them
1) README.maintainers and README.Debian contain old python version numbers.
I've changed them to automatically contain the correct version number.
2) The copyright file is for python2.4. I've copied in the appropriated text
for the main license (just years and version numbers have changed). I've not
checked the licenses for the 'incorporated programs', so the copyright
notice could potentially be out of date
Also: as far as I can see, the files debian/python.desktop and
debian/README.Debian aren't being used for anything. Can they be deleted?
diff -Nur debian.old/copyright debian/copyright
--- debian.old/copyright 2007-10-14 21:34:05.000000000 +0200
+++ debian/copyright 2007-10-14 21:38:53.000000000 +0200
@@ -69,7 +69,13 @@
2.3.2 2.3.1 2002-2003 PSF yes
2.3.3 2.3.2 2002-2003 PSF yes
2.3.4 2.3.3 2004 PSF yes
+ 2.3.5 2.3.4 2005 PSF yes
2.4 2.3 2004 PSF yes
+ 2.4.1 2.4 2005 PSF yes
+ 2.4.2 2.4.1 2005 PSF yes
+ 2.4.3 2.4.2 2006 PSF yes
+ 2.5 2.4 2006 PSF yes
+ 2.5.1 2.5 2007 PSF yes
Footnotes:
@@ -105,9 +111,9 @@
prepare derivative works, distribute, and otherwise use Python
alone or in any derivative version, provided, however, that PSF's
License Agreement and PSF's notice of copyright, i.e., "Copyright (c)
-2001, 2002, 2003, 2004 Python Software Foundation; All Rights Reserved"
-are retained in Python alone or in any derivative version prepared
-by Licensee.
+2001, 2002, 2003, 2004, 2005, 2006, 2007 Python Software Foundation;
+All Rights Reserved" are retained in Python alone or in any derivative
+version prepared by Licensee.
3. In the event Licensee prepares a derivative work that is based on
or incorporates Python or any part thereof, and wants to make
@@ -286,7 +292,6 @@
OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-
Licenses and Acknowledgements for Incorporated Software
=======================================================
diff -Nur debian.old/README.Debian debian/README.Debian
--- debian.old/README.Debian 2007-10-14 21:34:05.000000000 +0200
+++ debian/README.Debian 1970-01-01 01:00:00.000000000 +0100
@@ -1,8 +0,0 @@
-The documentation for this package is in /usr/share/doc/python2.4/.
-
-A draft of the "Debian Python Policy" can be found in
-
- /usr/share/doc/python
-
-Sometime it will be moved to /usr/share/doc/debian-policy in the
-debian-policy package.
diff -Nur debian.old/README.Debian.in debian/README.Debian.in
--- debian.old/README.Debian.in 1970-01-01 01:00:00.000000000 +0100
+++ debian/README.Debian.in 2007-10-14 21:37:12.000000000 +0200
@@ -0,0 +1,8 @@
+The documentation for this package is in /usr/share/doc/@PVER@/.
+
+A draft of the "Debian Python Policy" can be found in
+
+ /usr/share/doc/python
+
+Sometime it will be moved to /usr/share/doc/debian-policy in the
+debian-policy package.
diff -Nur debian.old/README.maintainers debian/README.maintainers
--- debian.old/README.maintainers 2007-10-14 21:34:05.000000000 +0200
+++ debian/README.maintainers 1970-01-01 01:00:00.000000000 +0100
@@ -1,88 +0,0 @@
-
-Hints for maintainers of Debian packages of Python extensions
--------------------------------------------------------------
-
-Most of the content of this README can be found in the Debian Python policy.
-See /usr/share/doc/python/python-policy.txt.gz.
-
-Documentation Tools
--------------------
-
-If your package ships documentation produced in the Python
-documentation format, you can generate it at build-time by
-build-depending on python2.4-dev, and you will find the
-templates, tools and scripts in /usr/lib/python2.4/doc/tools --
-adjust your build scripts accordingly.
-
-
-Makefile.pre.in issues
-----------------------
-
-Python comes with a `universal Unix Makefile for Python extensions' in
-/usr/lib/python2.4/config/Makefile.pre.in (with Debian, this is included
-in the python-dev package), which is used by most Python extensions.
-
-In general, packages using the Makefile.pre.in approach can be packaged
-simply by running dh_make or by using one of debhelper's rules' templates
-(see /usr/doc/debhelper/examples/). Makefile.pre.in works fine with e.g.
-"make prefix=debian/tmp/usr install".
-
-One glitch: You may be running into the problem that Makefile.pre.in
-doesn't try to create all the directories when they don't exist. Therefore,
-you may have to create them manually before "make install". In most cases,
-the following should work:
-
- ...
- dh_installdirs /usr/lib/python2.4
- $(MAKE) prefix=debian/tmp/usr install
- ...
-
-
-Byte-compilation
-----------------
-
-For speed reasons, Python internally compiles source files into a byte-code.
-To speed up subsequent imports, it tries to save the byte-code along with
-the source with an extension .pyc (resp. pyo). This will fail if the
-libraries are installed in a non-writable directory, which may be the
-case for /usr/lib/python2.4/.
-
-Not that .pyc and .pyo files should not be relocated, since for debugging
-purposes the path of the source for is hard-coded into them.
-
-To precompile files in batches after installation, Python has a script
-compileall.py, which compiles all files in a given directory tree. The
-Debian version of compileall has been enhanced to support incremental
-compilation and to feature a ddir (destination dir) option. ddir is
-used to compile files in debian/usr/lib/python/ when they will be
-installed into /usr/lib/python/.
-
-
-Currently, there are two ways to use compileall for Debian packages. The
-first has a speed penalty, the second has a space penalty in the package.
-
-1.) Compiling and removing .pyc files in postinst/prerm:
-
- Use dh_python(1) from the debhelper packages to add commands to byte-
- compile on installation and to remove the byte-compiled files on removal.
- Your package has to build-depend on: debhelper (>= 4.1.67), python.
-
- In /usr/share/doc/python2.4, you'll find sample.postinst and sample.prerm.
- If you set the directory where the .py files are installed, these
- scripts will install and remove the .pyc and .pyo files for your
- package after unpacking resp. before removing the package.
-
-2.) Compiling the .pyc files `out of place' during installation:
-
- As of 1.5.1, compileall.py allows you to specify a faked installation
- directory using the "-d destdir" option, so that you can precompile
- the files in their temporary directory
- (e.g. debian/tmp/usr/lib/python2.1/site-packages/PACKAGE).
-
-
-
- 11/02/98
- Gregor Hoffleit <[EMAIL PROTECTED]>
-
-
-Last modified: 2001-12-14
diff -Nur debian.old/README.maintainers.in debian/README.maintainers.in
--- debian.old/README.maintainers.in 1970-01-01 01:00:00.000000000 +0100
+++ debian/README.maintainers.in 2007-10-14 21:37:12.000000000 +0200
@@ -0,0 +1,88 @@
+
+Hints for maintainers of Debian packages of Python extensions
+-------------------------------------------------------------
+
+Most of the content of this README can be found in the Debian Python policy.
+See /usr/share/doc/python/python-policy.txt.gz.
+
+Documentation Tools
+-------------------
+
+If your package ships documentation produced in the Python
+documentation format, you can generate it at build-time by
+build-depending on @[EMAIL PROTECTED], and you will find the
+templates, tools and scripts in /usr/lib/@PVER@/doc/tools --
+adjust your build scripts accordingly.
+
+
+Makefile.pre.in issues
+----------------------
+
+Python comes with a `universal Unix Makefile for Python extensions' in
+/usr/lib/@PVER@/config/Makefile.pre.in (with Debian, this is included
+in the python-dev package), which is used by most Python extensions.
+
+In general, packages using the Makefile.pre.in approach can be packaged
+simply by running dh_make or by using one of debhelper's rules' templates
+(see /usr/doc/debhelper/examples/). Makefile.pre.in works fine with e.g.
+"make prefix=debian/tmp/usr install".
+
+One glitch: You may be running into the problem that Makefile.pre.in
+doesn't try to create all the directories when they don't exist. Therefore,
+you may have to create them manually before "make install". In most cases,
+the following should work:
+
+ ...
+ dh_installdirs /usr/lib/@PVER@
+ $(MAKE) prefix=debian/tmp/usr install
+ ...
+
+
+Byte-compilation
+----------------
+
+For speed reasons, Python internally compiles source files into a byte-code.
+To speed up subsequent imports, it tries to save the byte-code along with
+the source with an extension .pyc (resp. pyo). This will fail if the
+libraries are installed in a non-writable directory, which may be the
+case for /usr/lib/@PVER@/.
+
+Not that .pyc and .pyo files should not be relocated, since for debugging
+purposes the path of the source for is hard-coded into them.
+
+To precompile files in batches after installation, Python has a script
+compileall.py, which compiles all files in a given directory tree. The
+Debian version of compileall has been enhanced to support incremental
+compilation and to feature a ddir (destination dir) option. ddir is
+used to compile files in debian/usr/lib/python/ when they will be
+installed into /usr/lib/python/.
+
+
+Currently, there are two ways to use compileall for Debian packages. The
+first has a speed penalty, the second has a space penalty in the package.
+
+1.) Compiling and removing .pyc files in postinst/prerm:
+
+ Use dh_python(1) from the debhelper packages to add commands to byte-
+ compile on installation and to remove the byte-compiled files on removal.
+ Your package has to build-depend on: debhelper (>= 4.1.67), python.
+
+ In /usr/share/doc/@PVER@, you'll find sample.postinst and sample.prerm.
+ If you set the directory where the .py files are installed, these
+ scripts will install and remove the .pyc and .pyo files for your
+ package after unpacking resp. before removing the package.
+
+2.) Compiling the .pyc files `out of place' during installation:
+
+ As of 1.5.1, compileall.py allows you to specify a faked installation
+ directory using the "-d destdir" option, so that you can precompile
+ the files in their temporary directory
+ (e.g. debian/tmp/usr/lib/python2.1/site-packages/PACKAGE).
+
+
+
+ 11/02/98
+ Gregor Hoffleit <[EMAIL PROTECTED]>
+
+
+Last modified: 2007-10-14
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
