[Pkg-octave-commit] r1281 - octave-pkg-dev/trunk/debian
Rafael Laboissiere
rafael at alioth.debian.org
Mon Feb 25 23:05:44 UTC 2008
Author: rafael
Date: 2008-02-25 23:05:44 +0000 (Mon, 25 Feb 2008)
New Revision: 1281
Modified:
octave-pkg-dev/trunk/debian/README.Debian
Log:
Added README text
Modified: octave-pkg-dev/trunk/debian/README.Debian
===================================================================
--- octave-pkg-dev/trunk/debian/README.Debian 2008-02-25 22:36:13 UTC (rev 1280)
+++ octave-pkg-dev/trunk/debian/README.Debian 2008-02-25 23:05:44 UTC (rev 1281)
@@ -1,6 +1,31 @@
octave-pkg-dev for Debian
-------------------------
-<possible notes regarding this package - if none, delete this file>
+This package provides the infrastructure for building Debian packages
+for the Octave add-ons, which are built/installed through the pkg.m
+system.
- -- Rafael Laboissiere <rafael at debian.org> Mon, 25 Feb 2008 10:11:27 +0100
+To use this package, make your add-on source package build-depends on
+octave-pkg-dev and add the following line to debian/rules:
+
+ include /usr/share/octave/debian/octave-pkg-dev.mk
+
+Also, 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 "SOURCFORGE = NO" in debian/rules.
+
+[1] http://octave.sourceforge.net/packages.html
+
+
+ -- Rafael Laboissiere <rafael at debian.org>, Tue, 26 Feb 2008 00:05:17 +0100
More information about the Pkg-octave-commit
mailing list