File: README

package info (click to toggle)
octave-pkg-dev 0.5.7
  • links: PTS, VCS
  • area: main
  • in suites: lenny
  • size: 124 kB
  • ctags: 44
  • sloc: perl: 32; makefile: 10
file content (49 lines) | stat: -rw-r--r-- 2,032 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
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/octave/debian/octave-pkg-dev.mk

Also, build-depend on debhelper (>= 6) and cdbs, and add a
debian/compat file containing "6".

Add ${octave:Depends} to the Depends field of the package in
debian/control.

Appropriate postinst and prerm scripts are automatically generated.
If the package needs its own maintainer scripts, add a line containing
#DEBHELPER# to it.  This tag will be appropriately substituted by
octave-pkg-dev.

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 defined 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 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".


 -- Rafael Laboissiere <rafael@debian.org>, Mon, 31 Mar 2008 22:36:22 +0200