- cabal-devel - Haskell.org

Missing modules
by Simon Peyton-Jones 06 May '10

06 May '10

Dear Cabal developers If you look at http://hackage.haskell.org/trac/ghc/ticket/3951 you'll see an example of a very confusing link-time error message. The ultimate cause was that a package author omitted one of the modules when listing the package manifest (in exposed and hidden modules). But there is no error when building the package -- the error only shows up when linking a complete application that uses the package. This is obviously bad. When Cabal builds the package, we should clearly check that no modules are omitted. You probably have a ticket on this already, but I thought I'd mention it. Simon

1 0

[Hackage] #683: cabal-install init should ask for Main-is for executables
by Hackage 05 May '10

05 May '10

#683: cabal-install init should ask for Main-is for executables ---------------------------------+------------------------------------------ Reporter: ezyang | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.2 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Main-is is a required field for executable sections, so cabal-install should ask for it. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/683> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #680: Spec should define the interpretation of the library and includes and search dirs
by Hackage 05 May '10

05 May '10

#680: Spec should define the interpretation of the library and includes and search dirs ----------------------------------+----------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal specification | Version: Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------------+----------------------------------------- See http://hackage.haskell.org/trac/ghc/ticket/3930 The Cabal spec should say how to interpret the `extra-libraries` and `library-dirs` fields in the installed package info. Specifically how this information is interpreted in relation to package dependencies which may also specify libraries and search paths. The interpretation should be that all the `extra-libraries` required by a installed package should be found in `library-dirs` given in that installed package info, or in the "standard" system linker path (as used by the standard system linker). That is, the `library-dirs` of dependent packages should not be used. For example: {{{ -- installed package gtk: extra-libraries: gtk-x11-2.0 library-dirs: depends: glib -- installed package glib: extra-libraries: glib-2.0 library-dirs: /opt/local/lib }}} We presume here that `/opt/local/lib` is not on the standard linker path. Then we should only look for the `gtk-x11-2.0` library on the paths specified in the gtk package, which in this case is empty, so that means only on the system linker path. If `gtk-x11-2.0` is in fact only in `/opt/local/lib` then this will and should fail. We should not use the library dirs of the `glib` package to find the libraries of the `gtk` package. The correct information for the above example would be to list `library- dirs: /opt/local/lib` for the gtk package also. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/680> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #678: Add framework to provide ad-hoc diagnostics for common failures
by Hackage 03 May '10

03 May '10

#678: Add framework to provide ad-hoc diagnostics for common failures ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Just as we have a system for doing various QA checks on cabal packages, perhaps we should have something to help users diagnose common problems with the system environment that crop up as e.g. linker errors. For example, a user reported in #haskell that the wx package failed to configure and reported that the `stdc++` C library was missing. We eventually discovered that although the standard C++ library was installed, it was not found by `gcc -lstdc++`. Installing the C++ components of gcc (ie the distro package that provides `g++`) fixed the issue, presumably because installing that package modified the standard gcc linker search path to include the location where `stdc++` was already installed. It would be good if after diagnosing this particular issue, it was easy to code up a test for this situation and add it into Cabal's `Simple` build system so that other users might get more helpful diagnostics in future. It does not need to be comprehensive, so it is ok to try and grok the output of linkers and to work just on some OSs or just with gcc for example. This might also help with common ghc problems. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/678> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #330: Support general documentation, not just haddock
by Hackage 03 May '10

03 May '10

#330: Support general documentation, not just haddock ----------------------------+----------------------------------------------- Reporter: fons | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ----------------------------+----------------------------------------------- Comment(by duncan): See additional suggestions in ticket #674. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/330#comment:6> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #668: Update simple distribution for LHC
by Hackage 29 Apr '10

29 Apr '10

#668: Update simple distribution for LHC ----------------------------------+----------------------------------------- Reporter: dmp | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.4 Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: 6.12.1 Platform: Mac OS | ----------------------------------+----------------------------------------- Cabal needs some updates for its LHC support. Two changes are needed (and implemented in the attached patch): 1) Change the hackRtsPackage to not fail with an error. The hackRtsPackage function was previously throwing an error when it found zero or more than one rts packages. The rts package is not needed in lhc, so the error is now ignored. This change now matches the behavior in the GHC distribution (Distribution/Simple/GHC.hs) 2) Change the value passed to the odir for compiling C files. The current code was doing a version check to catch a bug with GHC < 6.4. Since lhc is only version 0.9, it was also failing on the version check and passing an incorrect value to odir. Changed to use the correct value as with GHC > 6.4. I have attached a patch against the 1.8 branch that implements these changes. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/668> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #289: symlink binaries into ~/bin
by Hackage 29 Apr '10

29 Apr '10

#289: symlink binaries into ~/bin ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: cabal-install-0.8 Component: cabal-install tool | Version: Severity: normal | Keywords: Difficulty: easy (<4 hours) | Ghcversion: 6.8.2 Platform: | ---------------------------------+------------------------------------------ Changes (by gwern): * cc: gwern0@… (added) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/289#comment:19> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Haskell-cafe] Cabal package with BSD3 library and LGPL executable?
by Malcolm Wallace 29 Apr '10

29 Apr '10

On 29 Apr 2010, at 13:18, Ivan Lazar Miljenovic wrote: > Stephen Tetley <stephen.tetley(a)gmail.com> writes: >> Thanks. As far as the Cabal file goes - CppHs is LGPL, its in the >> included README that the GPL distinction is noticed. Possibly this >> isn't the clearest way of presenting things... > > Well, currently Cabal only lets you specify one license, so your > options > are to either use OtherLicense like Bulat suggested and then specify > in > the License file what's what, or else do as cpphs does. I suggest submitting a feature request for Cabal: permit separate licences on each executable stanza. Regards, Malcolm

1 0

Re: [Hackage] #215: Overhaul support for package's tests
by Hackage 28 Apr '10

28 Apr '10

#215: Overhaul support for package's tests ------------------------------+--------------------------------------------- Reporter: duncan | Owner: RichardG Type: task | Status: assigned Priority: normal | Milestone: Cabal-1.8 Component: Cabal library | Version: Severity: normal | Keywords: Difficulty: project(> week) | Ghcversion: 6.8.2 Platform: | ------------------------------+--------------------------------------------- Comment(by RichardG): Replying to [comment:13 tibbe]: > Thomas Tuegel will work on this as part of Google Summer of Code (with me as his mentor)... That's great news! I'll send him an email. (I did a little searching and didn't find much info on whether the project had been taken up or not.) It may be a good idea to reassign this bug to him to avoid confusion. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/215#comment:14> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #215: Overhaul support for package's tests
by Hackage 28 Apr '10

28 Apr '10

#215: Overhaul support for package's tests ------------------------------+--------------------------------------------- Reporter: duncan | Owner: RichardG Type: task | Status: assigned Priority: normal | Milestone: Cabal-1.8 Component: Cabal library | Version: Severity: normal | Keywords: Difficulty: project(> week) | Ghcversion: 6.8.2 Platform: | ------------------------------+--------------------------------------------- Comment(by tibbe): Replying to [comment:12 RichardG]: > I want to take this on. > > I'm very much in favor of having Cabal build and run external programs that print formatted data to stdout, which is then parsed and aggregated by Cabal. This makes it easier to integrate new testing libraries and also provides more control over how testing is performed (e.g., the HUnit tests give different results with 6.12.1 when compiled with -O and without). Thomas Tuegel will work on this as part of Google Summer of Code (with me as his mentor): http://socghop.appspot.com/gsoc/student_project/show/google/gsoc2010/haskel… I suggest you talk to Thomas if you're interested in working on this project. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/215#comment:13> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0