Op di, 30-05-2006 te 12:05 -0700, schreef Jeremy Shaw:
Hello,
I have a first cut of a template for cabalizing and debianizing haskell libraries. Do a,
darcs get http://www.n-heptane.com/nhlab/repos/cabalDebianTemplate
...and see the terse instructions in INSTRUCTIONS.txt. The instructions assume you already know the basics of cabal and debian.
I have used the template to debianize or cabalize+debianize a few third party libraries for local use, and it only takes 1-2 mins. Of course, for local use I don't bother to update all the descriptions in debian/control, etc.
This version does not generate profiling libraries -- so if we decide that it should, I will add that.
My current plan is something like this:
(1) Get a template hammered out that everyone likes (profiling, etc) (2) Write some newbie friendly documentation for it (3) Publish the docs on the wiki (4) Write an script to automate the template->specific package conversion process.
It is possible that (4) may get moved between (1) and (2) depending on how difficult and desirable it is.
If you have any suggestions or improvements let me know.
Well if a package would be based on this files with only the changes made were based on the instructions in the instruction file, I would not upload it to the Debian archive (if I were a DD), and from what I have seen on debian-mentors it isn't enough for sponsoring either.
Some points:
debian/control: * duplicate build-dependencies: debhelper, ghc6 and haskell-devscripts should not be Build-Depends-Indep
debian/rules: * drop the CFLAGS we don't build C libraries but Haskell packages, * drop DEB_HOST_GNU_TYPE and DEB_BUILD_GNU_TYPE as we don't call ./configure with these variables * drop the INSTALL_PROGRAM cruft, this is deprecated by dh_strip. * drop the configure target * don't use hyphens at the beginning of a command to ignore errors, for instance replace -./setup clean with if [ -x setup ] && [ -e .setup-config ] ; then ./setup clean ; fi * drop the unnecessary dh_FOO calls and commented out dh_FOO calls
You might want to look at the changes I made for the haskell-crypto [1] and haskell-newbinary [2] packages (I am not the maintainer, so he might not agree with all my changes) to see my ideas for the control and rules file.
[1] dget http://moonshine.dnsalias.org/debian/unstable/haskell-newbinary_0.0.20051211... [2] dget http://moonshine.dnsalias.org/debian/unstable/haskell-crypto_2.0.3-4.2_i386....
Finally packages which are intended to be uploaded to Debian should not be native packages but be cleanly split in a orig.tar.gz and a diff.gz and don't include the _darcs directory.
Just my 2cents
Greetings Arjan