[Python-modules-commits] r18759 - in packages/python-peak.rules/trunk/debian (README.source)

eriol-guest at users.alioth.debian.org eriol-guest at users.alioth.debian.org
Wed Sep 28 16:49:22 UTC 2011


    Date: Wednesday, September 28, 2011 @ 16:49:21
  Author: eriol-guest
Revision: 18759

Updated README.source

Modified:
  packages/python-peak.rules/trunk/debian/README.source

Modified: packages/python-peak.rules/trunk/debian/README.source
===================================================================
--- packages/python-peak.rules/trunk/debian/README.source	2011-09-28 16:44:07 UTC (rev 18758)
+++ packages/python-peak.rules/trunk/debian/README.source	2011-09-28 16:49:21 UTC (rev 18759)
@@ -1,24 +1,40 @@
-
 Upgrade to a new upstream
 =========================
 
-This package is a multi-upstream source package, i.e., its
-.orig.tar.gz is composed by several upstream tarballs, possibly
-released by independent authors.
+This package use multiple upstream tarballs support provided by source package
+format "3.0 (quilt)".
 
-To obtain a new orig tarball you can invoke the get-orig-source target
-of debian/rules as follows:
+To obtain new orig tarballs you have to specify package version inside
+debian/changelog, update module version in the $(PRIORITIZED_METHODS) Makefile
+variable inside debian/rules and then invoke the get-orig-source target of
+debian/rules as follows:
 
-   $ debian/rules get-orig-source
+    $ debian/rules get-orig-source
 
-If all goes well, that should leave around a .orig.tar.gz
+If all goes well, that should leave, inside the the current directory a tarball
+called
 
-Note that the target does not check whether creating a new upstream
-version is needed: invoke it only if you know that some of the
-upstream parts of this package need updates. Otherwise, use "apt-get
-source PACKAGE" to work on the latest uploaded upstream release.
+    PACKAGE_VERSION.orig.tar.gz
 
+    where PACKAGE is the source package name and VERSION is the version
+    specified in debian/changelog;
 
+and a two tarballs called
+
+    PACKAGE_VERSION.orig-rules.tar.gz
+
+    PACKAGE_VERSION.orig-EXTENSIONNAME-EXTENSIONVERSION.tar.gz
+
+    where EXTENSIONNAME and EXTENSIONVERSION are specified in the
+    $(PRIORITIZED_METHODS) Makefile variable inside debian/rules:
+    the only known extension, at the time of this packaging work, is
+    prioritized_methods so we can directly pertain to it.
+
+When using svn-buildpackage because --svn-download-orig argument
+doesn't work as expected (see #577140) *.orig tarballs must manually moved
+inside origDir.
+
+
 Package version
 ===============
 
@@ -30,21 +46,19 @@
 Adding a new contrib
 ====================
 
-As this package ships contribs for PEAK.rules, it is natural to expect
-that in the future new contribs will be added. To add one to the
-package follow a few simple rules:
+At the time of this packaging work only one contrib exists, but it is natural
+to expect that in the future new contribs will be added. To add one to the
+package a bit of refactoring is needed:
 
-1) add the module name (usually the egg name) to the $(UPSTREAMS)
-   Makefile variable in debian/rules
+1) $(PRIORITIZED_METHODS) must be renamed to something like $(CONTRIBS) to take
+   note of each contrib name and version
 
 2) add the per-contrib watch file as debian/NAME.watch, where NAME is
-   the module name
+   the contrib name
 
 3) add license and copyright information about the new module to
    debian/copyright
 
-4) run "debian/rules get-orig-source" to recreate the new tarball
+4) refactor get-orig-source to handle multiple contrib
 
-
- -- Stefano Zacchiroli <zack at debian.org>, Thu, 25 Jun 2009 15:30:02 +0200
-
+For a complete example you can look at python-peak.util's debian/rules.




More information about the Python-modules-commits mailing list