debian-haskell June 2006

debian-haskell@lists.urchin.earth.li

8 participants
7 discussions

Re: libghc6-wxhaskell-dev
by Isaac Jones 28 Oct '06

28 Oct '06

Looks like a new version of this package needs to be built, but I'm not really maintaining this package. Maybe the debian-haskell list can help? peace, isaac Martin Flack <martin(a)martinflack.com> writes: > Hi Isaac, > > I'm trying to install the package libghc6-wxhaskell-dev from > haskell-unsafe.alioth.debian.org so I can try writing some simple > Haskell programs on my Ubuntu Dapper desktop. > > Unfortunately I receive this error: > The following packages have unmet dependencies. > libghc6-wxhaskell-dev: Depends: ghc6 (< 6.2.3) but 6.4.1-2ubuntu2 is > to be installed > > Also the ghc package on the same repo seems to be 6.4.1-1 so I'm not > sure what to do. Do I have to find a 6.2.3 package and downgrade or is > there an update to libghc6-wxhaskell-dev available somewhere? > > I tried compiling the source but I get C++ errors. I'd rather figure it > out on a package level though. > > Thank you very much for any help you can give! > > Cheers, > Martin Flack

3 3

How best to split -dev and -prof files?
by Jeremy Shaw 02 Jul '06

02 Jul '06

Hello, I started working on building -prof .debs by default, but I ran into a minor snag. I do not see an easy way to seperate the generated files into the -dev and -prof packages -- all the files are lumped into the same directory tree. Here is the process I am using: 1) setup configure --enable-library-profiling 2) setup build 3) setup copy --copy-prefix $tmp The problem is, the build phase builds both the profiled and non-profiled version, and puts them in the same place. The best option I see at the moment is to use 'find' to find all the files that look like profiling enabled files and move them out of the -dev package into the -prof package. That seems error prone however. Does anyone have any suggestions? Perhaps cabal should provide better support for this operation? Thanks! j. ps. Currently I am using this find command, are there any thing other patterns I should look for? find . -name "*_p.a" -o -name "*.p_hi" -o -name "*.p_o"

2 1

RFS: c2hs -- C->Haskell Interface Generator
by Arjan Oosting 02 Jul '06

02 Jul '06

Hi people, I intent to adopt c2hs (#342801) and prepared an updated packages which upgrades the package to upstream version 0.14.5. The complete changelog can be found below. I am searching for a sponsor to check and upload the package (I am still in the NM queue). The package is linda and lintian clean and can be found on my website [1]. The source can be downloaded by doing dget http://moonshine.dnsalias.org/debian/unstable/c2hs_0.14.5-1_i386.changes Greetings Arjan Oosting [1] http://moonshine.dnsalias.org/debian/unstable * New upstream release. Closes: #372836 - no longer ships a library for ghc6. * New maintainer. Closes: #342801 * debian/c2hs-doc.doc-base: change section to devel. * added debian/control.in - drop the libghc6-c2hs-dev package. - use $ghc6_app_bdeps, $ghc6_arches substitution variables from update-haskell-control to get the build dependency on ghc6 and architecture list for c2hs. - replace ${Source-Version} with ${binary:Version} and ${source:Version} to make the package binNMU safe. - add build dependency on dpkg-dev (>= 1.13.19) which introduces ${binary:Version} and ${source:Version}. - move groff and linuxdoc-tools to Build-Depends-Indep. * debian/copyright: add copyright notice for the manual which is licensed under the GNU Free Document License. * debian/patches/*: remove old patches and change to dpatch. * debian/rules: change from cdbs to debhelper. * debian/watch: upgrade to format version 3.

2 5

GHC 6.4.2
by John Goerzen 30 Jun '06

30 Jun '06

Hi, I'm growing increasingly concerned that ghc 6.4.2 is not yet in sid. It appears to fix a number of bugs, including compatibility issues with the gcc version that will be in etch. Once ghc 6.4.2 does hit sid, we'll still need time to get all the Haskell packages rebuilt. What are the plans for this? Ian, do you need any help? Thanks, -- John

3 5

RFS: frown -- LALR(k) parser generator for Haskell 98
by Arjan Oosting 27 Jun '06

27 Jun '06

Hi people, I am searching for a sponsor for frown. Frown is a parser generator for Haskell. It has similar syntax to Happy, another parser generator for Haskell, but frown has a couple of features not found in happy. * Package name : frown Version : 0.6 Upstream Author : Ralf Hinze <ralf(a)informatik.uni-bonn.de> * URL : http://www.informatik.uni-bonn.de/~ralf/frown/index.html * License : GPL version 2 Description: LALR(k) parser generator for Haskell 98 I have packaged frown because it is a build-dependency of another package I am maintaining. The package can be downloaded from my website [1] and can the source package can be downloaded by doing dget http://moonshine.dnsalias.org/debian/unstable/frown_0.6.1-2_i386.changes When rebuilding the package don't forget to include the complete changelog and source by using the -sa -v0.6.0-0 flags when calling dpkg-buildpackage. Greetings Arjan Oosting [1] http://moonshine.dnsalias.org/debian/unstable Long description: Its salient features are: - The generated parsers are time and space efficient. On the downside, the parsers are quite large. - Frown generates four different types of parsers. As a common characteristic, the parsers are genuinely functional (ie 'table-free'); the states of the underlying LR automaton are encoded as mutually recursive functions. Three output formats use a typed stack representation, one format due to Ross Paterson (code=stackless) works even without a stack. - Encoding states as functions means that each state can be treated individually as opposed to a table driven-approach, which necessitates a uniform treatment of states. For instance, look-ahead is only used when necessary to resolve conflicts. - Frown comes with debugging and tracing facilities; the standard output format due to Doaitse Swierstra (code=standard) may be useful for teaching LR parsing. - Common grammatical patterns such as repetition of symbols can be captured using rule schemata. There are several predefined rule schemata. - Terminal symbols are arbitrary variable-free Haskell patterns or guards. Both terminal and nonterminal symbols may have an arbitrary number of synthesized attributes. - Frown comes with extensive documentation; several example grammars are included. . Furthermore, Frown supports the use of monadic lexers, monadic semantic actions, precedences and associativity, the generation of backtracking parsers, multiple start symbols, error reporting and a weak form of error correction. . Homepage: http://www.informatik.uni-bonn.de/~ralf/frown/index.html

1 0

First cut at cabal/debian template
by Jeremy Shaw 20 Jun '06

20 Jun '06

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. j.

4 5

should we provide -prof .debs by default?
by Jeremy Shaw 05 Jun '06

05 Jun '06

Hello, Recently I was trying to profile some code, and GHC complained that it could not find profiling versions of some 3rd party libraries I was using. According to the GHC manual: 5.2. Compiler options for profiling -prof: To make use of the profiling system all modules must be compiled and linked with the -prof option. Cabal already supports profiling (from the cabal manual section 3.1.3): --enable-library-profiling or -p Request that an additional version of the library with profiling features enabled be built and installed (only for implementations that support profiling). So, perhaps in addition to the libghc6-*-dev packages, we should be providing libghc6-*-prof packages by default? Or is there some trick that will let me profile my application even if I link against some non-profiling-enabled modules? j.

4 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

debian-haskell June 2006