[Pkg-haskell-commits] r825 - in /packages/haskell-devscripts/trunk: dh_haskell dh_haskell_build dh_haskell_buildinst dh_haskell_install
arjan at users.alioth.debian.org
arjan at users.alioth.debian.org
Sun Dec 30 18:09:26 UTC 2007
Author: arjan
Date: Sun Dec 30 18:09:26 2007
New Revision: 825
URL: http://svn.debian.org/wsvn/pkg-haskell/?sc=1&rev=825
Log:
[project @ update man page to include instructions for profiling package]
Original author: jeremy.shaw at linspireinc.com
Date: 2006-08-11 21:06:51+00:00
Modified:
packages/haskell-devscripts/trunk/dh_haskell
packages/haskell-devscripts/trunk/dh_haskell_build
packages/haskell-devscripts/trunk/dh_haskell_buildinst
packages/haskell-devscripts/trunk/dh_haskell_install
Modified: packages/haskell-devscripts/trunk/dh_haskell
URL: http://svn.debian.org/wsvn/pkg-haskell/packages/haskell-devscripts/trunk/dh_haskell?rev=825&op=diff
==============================================================================
--- packages/haskell-devscripts/trunk/dh_haskell (original)
+++ packages/haskell-devscripts/trunk/dh_haskell Sun Dec 30 18:09:26 2007
@@ -36,7 +36,7 @@
dh_haskell is a debhelper program that helps with building Haskell libraries.
-It does several things. It can generat postinst and prerm scripts when
+It does several things. It can generate postinst and prerm scripts when
necessary. It automates building libraries for the different supported
Haskell systems in Debian. It generates substvars for your control
file so that the library packages depend on the appropriate packages.
@@ -46,10 +46,15 @@
dh_haskell assumes that your packages are adhering to the draft Haskell policy.
-Your control file must build the binary library files using packages named
-libI<type>-I<name>-dev, where I<type> is ghc5, ghc6, or nhc98; and
-I<name> is the name of your package. These packages should be Architecture:
-any.
+Your control file must build the binary library files using packages
+named libI<type>-I<name>-I<variation>, where I<type> is ghc5, ghc6, or
+nhc98; I<name> is the name of your package; and I<variation> is dev or
+prof. These packages should be Architecture: any.
+
+The I<prof> package contains profiling enabled libraries. Currently
+only GHC supports profiling. Due to restrictions of the GHC compiler,
+if you provide a I<dev> package you should also provide a
+corresponding I<prof> package.
If you build a Hugs package, name it libhugs-I<name>. However, dh_haskell
will also accept libhugs-I<name>-dev for consistency. Most Hugs packages
@@ -85,9 +90,13 @@
That's it. dh_haskell does the rest.
-=head1 EXAMPLE
+=head1 EXAMPLES
See the Debian source package for hunit.
+
+also see:
+
+darcs get --partial http://www.n-heptane.com/nhlab/repos/cabalDebianTemplate/
=cut
Modified: packages/haskell-devscripts/trunk/dh_haskell_build
URL: http://svn.debian.org/wsvn/pkg-haskell/packages/haskell-devscripts/trunk/dh_haskell_build?rev=825&op=diff
==============================================================================
--- packages/haskell-devscripts/trunk/dh_haskell_build (original)
+++ packages/haskell-devscripts/trunk/dh_haskell_build Sun Dec 30 18:09:26 2007
@@ -36,7 +36,7 @@
dh_haskell is a debhelper program that helps with building Haskell libraries.
-It does several things. It can generat postinst and prerm scripts when
+It does several things. It can generate postinst and prerm scripts when
necessary. It automates building libraries for the different supported
Haskell systems in Debian. It generates substvars for your control
file so that the library packages depend on the appropriate packages.
@@ -46,10 +46,15 @@
dh_haskell assumes that your packages are adhering to the draft Haskell policy.
-Your control file must build the binary library files using packages named
-libI<type>-I<name>-dev, where I<type> is ghc5, ghc6, or nhc98; and
-I<name> is the name of your package. These packages should be Architecture:
-any.
+Your control file must build the binary library files using packages
+named libI<type>-I<name>-I<variation>, where I<type> is ghc5, ghc6, or
+nhc98; I<name> is the name of your package; and I<variation> is dev or
+prof. These packages should be Architecture: any.
+
+The I<prof> package contains profiling enabled libraries. Currently
+only GHC supports profiling. Due to restrictions of the GHC compiler,
+if you provide a I<dev> package you should also provide a
+corresponding I<prof> package.
If you build a Hugs package, name it libhugs-I<name>. However, dh_haskell
will also accept libhugs-I<name>-dev for consistency. Most Hugs packages
@@ -85,9 +90,13 @@
That's it. dh_haskell does the rest.
-=head1 EXAMPLE
+=head1 EXAMPLES
See the Debian source package for hunit.
+
+also see:
+
+darcs get --partial http://www.n-heptane.com/nhlab/repos/cabalDebianTemplate/
=cut
Modified: packages/haskell-devscripts/trunk/dh_haskell_buildinst
URL: http://svn.debian.org/wsvn/pkg-haskell/packages/haskell-devscripts/trunk/dh_haskell_buildinst?rev=825&op=diff
==============================================================================
--- packages/haskell-devscripts/trunk/dh_haskell_buildinst (original)
+++ packages/haskell-devscripts/trunk/dh_haskell_buildinst Sun Dec 30 18:09:26 2007
@@ -36,7 +36,7 @@
dh_haskell is a debhelper program that helps with building Haskell libraries.
-It does several things. It can generat postinst and prerm scripts when
+It does several things. It can generate postinst and prerm scripts when
necessary. It automates building libraries for the different supported
Haskell systems in Debian. It generates substvars for your control
file so that the library packages depend on the appropriate packages.
@@ -46,10 +46,15 @@
dh_haskell assumes that your packages are adhering to the draft Haskell policy.
-Your control file must build the binary library files using packages named
-libI<type>-I<name>-dev, where I<type> is ghc5, ghc6, or nhc98; and
-I<name> is the name of your package. These packages should be Architecture:
-any.
+Your control file must build the binary library files using packages
+named libI<type>-I<name>-I<variation>, where I<type> is ghc5, ghc6, or
+nhc98; I<name> is the name of your package; and I<variation> is dev or
+prof. These packages should be Architecture: any.
+
+The I<prof> package contains profiling enabled libraries. Currently
+only GHC supports profiling. Due to restrictions of the GHC compiler,
+if you provide a I<dev> package you should also provide a
+corresponding I<prof> package.
If you build a Hugs package, name it libhugs-I<name>. However, dh_haskell
will also accept libhugs-I<name>-dev for consistency. Most Hugs packages
@@ -85,9 +90,13 @@
That's it. dh_haskell does the rest.
-=head1 EXAMPLE
+=head1 EXAMPLES
See the Debian source package for hunit.
+
+also see:
+
+darcs get --partial http://www.n-heptane.com/nhlab/repos/cabalDebianTemplate/
=cut
Modified: packages/haskell-devscripts/trunk/dh_haskell_install
URL: http://svn.debian.org/wsvn/pkg-haskell/packages/haskell-devscripts/trunk/dh_haskell_install?rev=825&op=diff
==============================================================================
--- packages/haskell-devscripts/trunk/dh_haskell_install (original)
+++ packages/haskell-devscripts/trunk/dh_haskell_install Sun Dec 30 18:09:26 2007
@@ -36,7 +36,7 @@
dh_haskell is a debhelper program that helps with building Haskell libraries.
-It does several things. It can generat postinst and prerm scripts when
+It does several things. It can generate postinst and prerm scripts when
necessary. It automates building libraries for the different supported
Haskell systems in Debian. It generates substvars for your control
file so that the library packages depend on the appropriate packages.
@@ -46,10 +46,15 @@
dh_haskell assumes that your packages are adhering to the draft Haskell policy.
-Your control file must build the binary library files using packages named
-libI<type>-I<name>-dev, where I<type> is ghc5, ghc6, or nhc98; and
-I<name> is the name of your package. These packages should be Architecture:
-any.
+Your control file must build the binary library files using packages
+named libI<type>-I<name>-I<variation>, where I<type> is ghc5, ghc6, or
+nhc98; I<name> is the name of your package; and I<variation> is dev or
+prof. These packages should be Architecture: any.
+
+The I<prof> package contains profiling enabled libraries. Currently
+only GHC supports profiling. Due to restrictions of the GHC compiler,
+if you provide a I<dev> package you should also provide a
+corresponding I<prof> package.
If you build a Hugs package, name it libhugs-I<name>. However, dh_haskell
will also accept libhugs-I<name>-dev for consistency. Most Hugs packages
@@ -85,9 +90,13 @@
That's it. dh_haskell does the rest.
-=head1 EXAMPLE
+=head1 EXAMPLES
See the Debian source package for hunit.
+
+also see:
+
+darcs get --partial http://www.n-heptane.com/nhlab/repos/cabalDebianTemplate/
=cut
More information about the Pkg-haskell-commits
mailing list