Upgrade to a new upstream
=========================

This package use multiple upstream tarballs support provided by source package
format "3.0 (quilt)".

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

If all goes well, that should leave, inside the the current directory a tarball
called

    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
===============

Note that, while the package has multiple upstream tarballs,
PEAK-Rules is considered the "main" tarball. This means, in
particular, that the package version comes from it.


Adding a new contrib
====================

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) $(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 contrib name

3) add license and copyright information about the new module to
   debian/copyright

4) refactor get-orig-source to handle multiple contrib

For a complete example you can look at python-peak.util's debian/rules.
