octave-pkg-dev for Debian
-------------------------

This package provides the infrastructure for building Debian packages
for the Octave add-ons, which are built/installed through the pkg.m
system.

To use this package, make your add-on source package build-depend on
octave-pkg-dev and add the following line to debian/rules:

    include /usr/share/cdbs/1/class/octave-pkg.mk

Also, build-depend on debhelper and cdbs.

Add ${octave:Depends} to the Depends field of the package in
debian/control. This ensures that dependencies in upstream's DESCRIPTION file
are copied into debian/control.

A get-orig-source target is also transparently provided.  It works
only for the packages distributed by the octave-forge project at
SourceForge [1].  If the upstream pkg does not come from SourceForge,
the developer can define its own get-orig-source rule (do not forget
to use a double-colon for the target).  To avoid the octave-pkg-dev
specific rule to run, defined "SOURCEFORGE = NO" in debian/rules.

[1] http://octave.sourceforge.net/packages.html

The make-orig-tarball rule will build the .orig.tar.gz upstream
tarball using the pkg tarball downloaded through get-orig-source.

In order to have octave-pkg-dev working properly, it is necessary that
the binary package is named "octave-something" in debian/control.

Automatic running of unit tests is provided.  This is done by
inspecting the .m and .cc files under the debian directory after the package is
built and detecting those containing "%!test" and/or "%!assert"
directives.  Additional tests not contained in the upstream source
files may be put in debian/check.m.

The clean target follows the convention of CDBS.  For specifying it,
use the DEB_MAKE_CLEAN_TARGET variable.  Its default value is "-C src clean".

 -- Thomas Weber <tweber@debian.org> Thu, 16 Feb 2012 15:55:15 +0100
