January 2012 - cabal-devel

[Hackage] #776: cabal check gives invalid duplicate modules warning
by Hackage 05 Jan '12

05 Jan '12

#776: cabal check gives invalid duplicate modules warning ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.2 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Given the Cabal file: {{{ cabal-version: >= 1.2 build-type: Simple name: test version: 4.1 license: GPL category: Test author: Test maintainer: Test synopsis: Test description: Test flag extended-library library if flag(extended-library) exposed-modules: Test else other-modules: Test }}} I get the {{{cabal check}}} output: {{{ The following warnings are likely affect your build negatively: * Duplicate modules in library: Test These warnings may cause trouble when distributing the package: * A 'license-file' is not specified. The following errors will cause portability problems on other environments: * The package is missing a Setup.hs or Setup.lhs script. Hackage would reject this package. }}} The error about Test being duplicate is incorrect - the flag means it will occur at most once. This bug is annoying for Hoogle, which wants to have a library exposing internal details, mainly for documentation purposes, and a normal library as well. Thanks, Neil -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/776> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #793: On OS X, warn about filenames that only differ in case
by Hackage 05 Jan '12

05 Jan '12

#793: On OS X, warn about filenames that only differ in case ----------------------------+----------------------------------------------- Reporter: tibbe | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- I managed to make Cabal fail to build a project by having {{{ Name: hamt Version: 0.1 License: BSD3 License-file: LICENSE Author: Johan Tibell Maintainer: johan.tibell(a)gmail.com Category: Data Build-type: Simple Cabal-version: >=1.2 Library Exposed-modules: HAMT Other-modules: PopCount Build-depends: base, vector C-sources: popcount.c }}} The result was: {{{ Building hamt-0.1... [1 of 2] Compiling PopCount ( PopCount.hs, dist/build/PopCount.o ) ld: duplicate symbol _popcount in dist/build/popcount.o and dist/build/PopCount.o for inferred architecture i386 }}} `_popcount` is only defined in `popcount.c`. Looking in `dist/` showed that there was only a popcount.o there (from the C file). Renaming `popcount.c` to `popc.c` solved the problem. Cabal ought to warn in this case. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/793> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #788: Optionally exposed modules / APIs should be banned
by Hackage 05 Jan '12

05 Jan '12

#788: Optionally exposed modules / APIs should be banned ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- It is a deliberate decision that packages cannot depend on package + flag combinations, only on packages. The point is that flags are not supposed to change the API of a package. This needs to be enforced. Consider a real example (from Chart package: http://hackage.haskell.org/packages/archive/Chart/0.14/Chart.cabal) {{{ if flag(gtk) build-depends: gtk >= 0.9.11 exposed-modules: Graphics.Rendering.Chart.Gtk }}} The criterion package depends on Chart and imports `Graphics.Rendering.Chart.Gtk` meaning that it breaks if you build Chart with the gtk flag turned off. The solution is that Chart should be prevented from conditionally exposing modules. We should add a QA check that looks for exposed modules that are conditional on a flag. It is annoying but somewhat less bad for modules to change between platforms. Should it be a hard failure or just a warning? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/788> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #783: Weird brackets in function names on Haddock page
by Hackage 05 Jan '12

05 Jan '12

#783: Weird brackets in function names on Haddock page --------------------------------+------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | --------------------------------+------------------------------------------- Take a look at: http://hackage.haskell.org/packages/archive/harpy/0.4.3.0/doc/html/Harpy- Call.html Here the docs show very weird names such as conv[a9D8]. However, if we look at the source it has #ifndef __HADDOCK__, to make it look fine. But that's not being obeyed on Hackage, for some reason. -- Neil Mitchell -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/783> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

Re: [Hackage] #528: Permissions on "cabal fetch" files too tight
by Hackage 05 Jan '12

05 Jan '12

#528: Permissions on "cabal fetch" files too tight ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: low | Milestone: Component: cabal-install tool | Version: 1.6.0.1 Severity: minor | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Comment(by elga): * [http://www.releve-identite-operateur.fr/rio-bouygues.html rio bouygues] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/528#comment:2> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #287: make better use of existing build/failure reports (provide stats, alert authors)
by Hackage 05 Jan '12

05 Jan '12

#287: make better use of existing build/failure reports (provide stats, alert authors) --------------------------------+------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | --------------------------------+------------------------------------------- Comment(by elga): * [http://www.releve-identite-operateur.fr/numbero-de-virgin-mobile.html virgin mobile] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/287#comment:1> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #797: Cabal includes test suite dependencies when building the library
by Hackage 05 Jan '12

05 Jan '12

#797: Cabal includes test suite dependencies when building the library ----------------------------+----------------------------------------------- Reporter: tibbe | Owner: Type: defect | Status: new Priority: high | Milestone: Cabal-1.10 Component: Cabal library | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- `cabal configure` currently includes the test suite dependencies even without `--enable-tests`. This means that `cabal install <some lib>` will pull in e.g. test-framework, even though that isn't necessary to install the library. For example, given this configuration: {{{ library ... build-depends: base >= 3 && < 4.4, bytestring < 1.0, parsec >= 2.0 && < 3.1.1 if !os(windows) build-depends: unix >= 2 && < 3 test-suite simple ... build-depends: base < 4.4, bytestring < 0.10, HUnit < 1.3, network, test-framework < 0.4, test-framework-hunit < 0.3 test-suite uri ... build-depends: base < 4.4, HUnit < 1.3, network, test-framework < 0.4, test-framework-hunit < 0.3 }}} we get this: {{{ $ cabal configure -v ... Resolving dependencies... selecting network-2.3.0.2 (hackage) selecting HUnit-1.2.2.3 (installed) selecting base-4.3.0.0 (installed) selecting bytestring-0.9.1.8 (installed) selecting ffi-1.0 (installed) selecting ghc-prim-0.2.0.0 (installed) selecting integer-gmp-0.2.0.2 (installed) selecting rts-1.0 (installed) selecting test-framework-0.3.3 (installed) and discarding containers-0.3.0.0 and mtl-1.1.1.0 selecting ansi-terminal-0.5.5 (installed) selecting ansi-wl-pprint-0.6.3 (installed) selecting array-0.3.0.2 (installed) selecting containers-0.4.0.0 (installed) selecting extensible-exceptions-0.1.1.2 (installed) selecting hostname-1.0 (installed) selecting mtl-2.0.1.0 (installed) selecting old-locale-1.0.0.2 (installed) selecting random-1.0.0.3 (installed) selecting regex-base-0.93.2 (installed) selecting regex-posix-0.94.4 (installed) selecting test-framework-hunit-0.2.6 (installed) selecting time-1.2.0.3 (installed) selecting transformers-0.2.2.0 (installed) selecting unix-2.4.1.0 (installed) selecting xml-1.3.7 (installed) selecting parsec-2.1.0.1 (installed) and discarding parsec-3.1.0 }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/797> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 6

Re: [Hackage] #282: profiling versions of libraries not managed well
by Hackage 05 Jan '12

05 Jan '12

#282: profiling versions of libraries not managed well ---------------------------------+------------------------------------------ Reporter: SamB | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Keywords: profiling Difficulty: hard (< 1 day) | Ghcversion: 6.8.2 Platform: | ---------------------------------+------------------------------------------ Comment(by elga): * [http://www.releve-identite-operateur.fr/rio-bouygues.html rio bouygues] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/282#comment:10> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #578: Allow installation of distro packages
by Hackage 05 Jan '12

05 Jan '12

#578: Allow installation of distro packages ---------------------------------+------------------------------------------ Reporter: bos | Owner: Type: enhancement | Status: new Priority: normal | Milestone: _|_ Component: cabal-install tool | Version: Severity: normal | Keywords: Difficulty: project(> week) | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Comment(by elga): * [http://www.releve-identite-operateur.fr/numbero-de-virgin-mobile.html virgin mobile] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/578#comment:10> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #572: cabal update download too short when through privoxy
by Hackage 05 Jan '12

05 Jan '12

#572: cabal update download too short when through privoxy ---------------------------------+------------------------------------------ Reporter: wolverian | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: cabal-install tool | Version: 1.6.0.1 Severity: normal | Resolution: duplicate Keywords: | Difficulty: unknown Ghcversion: | Platform: Linux ---------------------------------+------------------------------------------ Comment(by elga): * [http://www.releve-identite-operateur.fr/rio-simyo.html simyo] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/572#comment:2> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0