May 2010 - cabal-devel

[Hackage] #682: 'cabal init' should try to set 'main-is' for executables
by Hackage 05 Mar '12

05 Mar '12

#682: 'cabal init' should try to set 'main-is' for executables ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Currently, `cabal init` will find modules and add them to the `exposed- modules` of a library. It should try to do something similar for executables. The `main-is` field is required for executables and any `other-modules` also need to be listed. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/682> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #685: cabal install does not work in /tmp/
by Hackage 05 Mar '12

05 Mar '12

#685: cabal install does not work in /tmp/ ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.3 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Wanting to to build darcs 2.4.3, I downloaded the tarball ( http://wiki.darcs.net/Releases/2.4 ) and uncompressed it in /tmp/ to run cabal install. I got the following error : cabal: Error: some packages failed to install: darcs-2.4.3 failed during the configure step. The exception was: ExitFailure 127 See http://hpaste.org/fastcgi/hpaste.fcgi/view?id=25412#a25412 for a full verbose log, but i think there is nothing informative to it. However, if I do "rm -fr dist" and try cabal install again, darcs build fine. Also, if I try in $HOME, cabal install works directly. Here are the versions of the software I'm using: cabal-install version 0.8.2 using version 1.8.0.4 of the Cabal library ghc 6.12.1 Linux distribution: Ubuntu 10.04 (Lucid Lynx). I hope this will help you! -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/685> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #686: cabal install - Codec.Compression.Zlib: incorrect header check
by Hackage 05 Mar '12

05 Mar '12

#686: cabal install - Codec.Compression.Zlib: incorrect header check ---------------------------------+------------------------------------------ Reporter: Monsikos | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.2 Severity: normal | Keywords: Zlib Difficulty: unknown | Ghcversion: 6.12.1 Platform: Windows | ---------------------------------+------------------------------------------ The command "cabal install packagename" fails with : "Codec.Compression.Zlib: incorret header check". The message appears while trying to extract the tar.gz file. I have manually updated Cabal (1.8.0.2), cabal-install(0.8.2) and zlib(0.5.2.0) but the error remains. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/686> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 12

[Hackage] #688: hard-coded path to configuration file
by Hackage 05 Mar '12

05 Mar '12

#688: hard-coded path to configuration file ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.2 Severity: minor | Keywords: Difficulty: easy (<4 hours) | Ghcversion: 6.10.4 Platform: Linux | ---------------------------------+------------------------------------------ I want to be able to tell {{{cabal}}} to read the configuration from a different place than {{{$HOME/.cabal/config}}}. The ultimate goal is to get rid of the non-standard {{{.cabal}}} directory altogether, so far careful {{{--package-db}}}/{{{--prefix}}} etc. juggling served me well; {{{config}}} is the last remaining file there. {{{ > cabal --version cabal-install version 0.8.2 using version 1.8.0.2 of the Cabal library }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/688> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 8

[Hackage] #690: document extra global options
by Hackage 05 Mar '12

05 Mar '12

#690: document extra global options ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.4 Severity: minor | Keywords: Difficulty: unknown | Ghcversion: 6.10.4 Platform: Linux | ---------------------------------+------------------------------------------ (split off from comment:1:ticket:688) > We don't list them all [such as --config-file] in the global --help so as not to clutter things, but then we need a way to let people know that there are extra global options and provide a way to get the help for them via some extended --help thing. Should go into a manual instead. You have already copied most of the good parts of the CPAN toolchain, installing man pages along binaries is one of the last things I am missing. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/690> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #691: cabal-install broken after update of cabal-install
by Hackage 05 Mar '12

05 Mar '12

#691: cabal-install broken after update of cabal-install ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: cabal-install-0.8 Component: cabal-install tool | Version: 1.8.0.2 Severity: major | Keywords: Difficulty: unknown | Ghcversion: 6.12.1 Platform: Mac OS | ---------------------------------+------------------------------------------ After I upgraded to a newer cabal-install my cabal-install broke again: I get a Bus Error when doing "cabal update" or "cabal install something". The version that was bundled with the Haskell platform worked fine, but now it's broken again. I'm not sure what it was that went wrong or how to debug this. The previous time I had Bus Errors I upgraded to the newest available Haskell Platform release and started from scratch. I would prefer not to do that again. However, I don't really know how to solve the Bus Error. Does anyone have a clue where to start? Or is there a way to undo my cabal-install upgrade? Here is some info about my system (on OSX 10.6): <pre> ghc -v Glasgow Haskell Compiler, Version 6.12.1, for Haskell 98, stage 2 booted by GHC version 6.10.4 </pre> <pre> cabal --version cabal-install version 0.8.0 using version 1.8.0.2 of the Cabal library </pre> I'm happy to help debugging and willing to test out possible solutions. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/691> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #667: Improve tools to manage ad-hoc package releases
by Hackage 05 Jan '12

05 Jan '12

#667: Improve tools to manage ad-hoc package releases ------------------------------+--------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: miscellaneous | Version: Severity: normal | Keywords: Difficulty: project(> week) | Ghcversion: Platform: | ------------------------------+--------------------------------------------- Hackage is suited for major software releases by package maintainers. It is not suited to distributing betas, daily snapshots or random forks, or patches of existing releases. For example a user may have some patch or bugfix for a package that they need. It takes time for maintainers to review and integrate these. Sometimes maintainers have little time, or they disagree with a patch approach or quality. It is right that maintainers have control over what is released on hackage. However there is a need for decentralised, ad-hoc and short term releases. We do not want to encourage the pollution of the package namespace with lots of short-term forks. One solution is to let users post package forks on their own webspace. We would want to extend cabal so that people can run: {{{ cabal install http://code.haskell.org/~user/foo/foo-fork-to-fix- blah-1.0.1.tar.gz }}} This makes it very decentralised. We may want to add some feature to hackage package pages to link to third-party forks. In addition to hosting and installing single packages it would be useful to be able to publish package collections. Of course this is exactly what a hackage archive is. We should provide easy tools to make and manage hackage archives that can be hosted on dumb http file servers. Going one step further, the hackage index format should be extended to make it more RESTful by including links to tarballs rather than just assuming that tarballs are found relative to the index file using some fixed layout. This would allow people to publish indexes that span multiple servers. This gets close to the concept of a package "search path" promoted by the searchpath project (http://searchpath.org/) Additonally, an index should allow us to point to source control repos rather than just to release tarballs. This kind of index would be useful for nighly builds. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/667> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #671: better error message for broken build tools
by Hackage 05 Jan '12

05 Jan '12

#671: better error message for broken build tools ------------------------------+--------------------------------------------- Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.4 Severity: normal | Keywords: Difficulty: easy (<4 hours) | Ghcversion: Platform: | ------------------------------+--------------------------------------------- Consider: {{{ Configuring haskell-src-exts-1.9.0... setup: happy version >=1.17 is required but the version of /usr/local/bin/happy could not be determined. }}} The actual problem is: {{{ /usr/local/bin/happy: error while loading shared libraries: libgmp.so.3: cannot open shared object file: No such file or directory }}} We could produce a better error message in this situation. If we get a non-0 exit code when we check the `--version` then we can probably safely report that the program is probably broken. Of course if we get some result text back and we cannot extract and parse the version number then that's different. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/671> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #663: Setup.hs doesn't look into ~/.cabal/bin for build tools.
by Hackage 05 Jan '12

05 Jan '12

#663: Setup.hs doesn't look into ~/.cabal/bin for build tools. ----------------------------------+----------------------------------------- Reporter: Axel Simon | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.3 Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: Platform: | ----------------------------------+----------------------------------------- Cabal currently only checks the current PATH for buildtools. If the user installs and new pre-processor with the default --user installation, these tools wind up in ~/.cabal/bin. However, cabal doesn't find these unless ~/.cabal/bin has been added to the PATH. This is irritating since it is then not possible to make a library depend on a cabal package that contains it's build tools: Even if cabal-install installs the build tools first, building the library still fails since the tools cannot be found. The solution is very simple: Add ~/.cabal/bin to the search path when looking for build tools! -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/663> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #697: Add "cabal build-dep" command
by Hackage 05 Jan '12

05 Jan '12

#697: Add "cabal build-dep" command ---------------------------------+------------------------------------------ Reporter: igloo | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: HEAD Severity: major | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ The [http://hackage.haskell.org/trac/ghc/wiki/HackageTesting hackage testing tool] needs a "cabal build-dep" command to work. I had an inadequate patch that was good enough for my experiments (http://osdir.com/ml/cabal-devel@haskell.org/2010-01/msg00029.html) but lack the familiarity with the cabal-install design necessary to implement it properly. Sadly, the patch no longer applies to cabal-install HEAD, and regardless, it would make things a lot easier if it Just Worked out of the box. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/697> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 7