January 2012 - cabal-devel

Re: [Hackage] #379: compiler directive of cabal-install's config file is case sensitive
by Hackage 05 Jan '12

05 Jan '12

#379: compiler directive of cabal-install's config file is case sensitive ---------------------------------+------------------------------------------ Reporter: phigley | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Resolution: fixed Keywords: | Difficulty: normal Ghcversion: 6.8.3 | Platform: Mac OS ---------------------------------+------------------------------------------ Comment(by edouard): le code Rio, ou code de Releve d'Identite Operateur, est un code a 12 caracteres fourni par son operateur de telephonie mobile vous permettant de conserver votre numero de telephone lorsque vous changez d'operateur. [http://www.releve-identite-operateur.fr/rio-simyo.html simyo] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/379#comment:4> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #701: Help packages to avoid linker symbol clashes
by Hackage 05 Jan '12

05 Jan '12

#701: Help packages to avoid linker symbol clashes ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.3 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Currently it is all too easy to end up with silently clashing linker symbols. The prime example is C code linked into a Haskell package. Multiple versions of the same package will define the same linker symbols. The system linker is happy to just pick the first occurrence of a symbol (though the ghci linker is stricter). This can cause havoc if the behaviour of the C code changes from one version of the package to another (see for example the problem with mmap and darcs, ticket #700). There are a number of things we could do to improve the situation. * We could make it easier to make versioned C symbols in the C code used in a Haskell package by providing cpp macros. * We could explicitly check for unversioned C symbols in Haskell libs * We could try linking Haskell libs in such a way that the C symbols are not visible and thus cannot clash, but it would also mean they are not exported for other libs to use. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/701> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #803: cabal test after cabal configure --enable-tests without cabal build creates obscure output
by Hackage 05 Jan '12

05 Jan '12

#803: cabal test after cabal configure --enable-tests without cabal build creates obscure output ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- It wasn't obvious to me that cabal build would be required before cabal test. Can cabal test automatically run cabal build? Otherwise a message should be shown telling the user to run cabal build. Here is an example output {{{ >>> Test suite runtests: RUNNING... >>> Test suite runtests: FAIL >>> Test suite logged to: dist/test/persistent-0.4.0.1-runtests.log >>> Test suite runtests: RUNNING... >>> Test suite runtests: FAIL >>> Test suite logged to: dist/test/persistent-0.4.0.1-runtests.log Test suite runtests: FAIL Test suite logged to: dist/test/persistent-0.4.0.1-runtests.log 0 of 1 test suites (0 of 1 test cases) passed. }}} The log is exactly the same as the output -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/803> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

Re: [Hackage] #605: Distribution\Client\Dependency\TopDown.hs:169:37-73: Non-exhaustive patterns in lambda
by Hackage 05 Jan '12

05 Jan '12

#605: Distribution\Client\Dependency\TopDown.hs:169:37-73: Non-exhaustive patterns in lambda ----------------------------+----------------------------------------------- Reporter: fasta | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Resolution: duplicate Keywords: | Difficulty: unknown Ghcversion: | Platform: ----------------------------+----------------------------------------------- Comment(by edouard): Vous pourrez vous procurer votre numero rio Orange, son numero rio SFR ou encore votre numero rio Bouygues en un clin d'oeil ! [http://www.releve- identite-operateur.fr/rio-bouygues.html rio bouygues] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/605#comment:3> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #601: cabal setup doesn't respect --prefix
by Hackage 05 Jan '12

05 Jan '12

#601: cabal setup doesn't respect --prefix ----------------------------+----------------------------------------------- Reporter: zooko | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Resolution: wontfix Keywords: | Difficulty: unknown Ghcversion: | Platform: ----------------------------+----------------------------------------------- Comment(by edouard): Ce site met a votre disposition toutes uns informations dont vous avez besoin pour la migration 100% reussie vers et depuis les principaux operateurs de telephonie mobiun ! [http://www.releve-identite-operateur.fr /numbero-de-virgin-mobile.html virgin mobile] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/601#comment:8> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #453: "cabal fetch" should take output arguments
by Hackage 05 Jan '12

05 Jan '12

#453: "cabal fetch" should take output arguments ----------------------------------+----------------------------------------- Reporter: gregorycollins | Owner: Type: enhancement | Status: new Priority: high | Milestone: cabal-install-0.8 Component: cabal-install tool | Version: HEAD Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: 6.10.1 Platform: | ----------------------------------+----------------------------------------- Comment(by edouard): Portabilite, portage, transfert de numero de telephone, un code Rio ou Releve d'Identite Operateur peut presenter differentes appellations. Toutefois, l'objectif reste le meme: changer d'operateur de telephonie mobiun tout en gardant son numero de telephone actuel. [http://www.releve- identite-operateur.fr/rio-simyo.html simyo] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/453#comment:11> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #262: Check for required C libraries during configure
by Hackage 05 Jan '12

05 Jan '12

#262: Check for required C libraries during configure ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: closed Priority: high | Milestone: Cabal-1.6 Component: Cabal library | Version: 1.2.3.0 Severity: normal | Resolution: fixed Keywords: | Difficulty: easy (<4 hours) Ghcversion: 6.8.2 | Platform: ----------------------------+----------------------------------------------- Comment(by edouard): A l'image du RIB bancaire, un code RIO est un identifiant unique attribue a la ligne et a un contrat client permettant d'identifier son demande de portabilite vers un autre operateur. [http://www.releve-identite- operateur.fr/rio-bouygues.html rio bouygues] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/262#comment:18> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #458: inconsistent use of CPPFLAGS, LDFLAGS etc with build-type Configure
by Hackage 05 Jan '12

05 Jan '12

#458: inconsistent use of CPPFLAGS, LDFLAGS etc with build-type Configure ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: defect | Status: new Priority: high | Milestone: Cabal-1.8 Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: | ----------------------------+----------------------------------------------- Comment(by edouard): le code Rio, ou code de Releve d'Identite Operateur, est un numero a 12 caracteres fourni par votre operateur de telephonie mobile vous permettant de conserver votre numero de telephone lorsque vous changez d'operateur. [http://www.releve-identite-operateur.fr/numbero-de-virgin-mobile.html virgin mobile] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/458#comment:6> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #814: Avoid orphan flexible instances in Cabal-TestSuite documentation
by Hackage 05 Jan '12

05 Jan '12

#814: Avoid orphan flexible instances in Cabal-TestSuite documentation ----------------------------------+----------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: User guide | Version: 1.10.1.0 Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: Platform: | ----------------------------------+----------------------------------------- The example code shown in http://www.haskell.org/cabal/release/cabal-1.10.1.0/doc/users-guide/#test- suites needs FlexibleInstances, and the instance is orphan, too. Although this code is not intended to be used in most packages, it still looks like those instances are necessary or at least good style. I suggest to replace the generic pair by a custom data type like {{{ data TestCase = TestCase String Bool instance TestOptions TestCase where ... }}} in the documentation. Since Cabal is a widely used library, it has automatically an educational aspect. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/814> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

Re: [Hackage] #598: Bogus build failures on HackageDB
by Hackage 05 Jan '12

05 Jan '12

#598: Bogus build failures on HackageDB --------------------------------+------------------------------------------- Reporter: mboes | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: hackageDB website | Version: Severity: normal | Resolution: fixed Keywords: | Difficulty: unknown Ghcversion: | Platform: --------------------------------+------------------------------------------- Comment(by edouard): Termine le parcours du combattant ! les procedures, aujourd'hui tres simplifiees, sont accessibles en quelques clics seulement. [http://www .releve-identite-operateur.fr/rio-bouygues.html rio bouygues] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/598#comment:12> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0