May 2011 - cabal-devel

[Hackage] #800: Cabal won't update
by Hackage 05 Jan '12

05 Jan '12

#800: Cabal won't update ----------------------------+----------------------------------------------- Reporter: mcandre | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Specs: * cabal-install 0.8.2 * Cabal 1.8.0.6 * GHC 6.12.3 * Mac OS X 10.6.6 * !MacBook Pro 5,1 Trace: {{{ $ cabal update Downloading the latest package list from hackage.haskell.org Warning: The package list for 'hackage.haskell.org' is 20 days old. Run 'cabal update' to get the latest list of available packages. }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/800> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #836: Provide the state of Cabal flags in an auto-generated module
by Hackage 05 Jan '12

05 Jan '12

#836: Provide the state of Cabal flags in an auto-generated module ----------------------------+----------------------------------------------- Reporter: lemming | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.10.0.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- I would like to query the state of cabal flags at configure time without CPP hackery. I would prefer to import an autogenerated module, that contains Bool variables with the names of the Cabal flags, just like the Paths module contains the paths of installed data files. For instance if my Cabal file contains {{{ Flag buildExamples description: Build example executables default: False Flag buildTests description: Build test suite default: True Flag debug description: Compile with debug messages default: False }}} and I install the package by {{{ $ cabal install -fdebug }}} then the autogenerated module shall contain {{{ module Flags_mypkg where -- | Build example executables buildExamples :: Bool buildExamples = False -- | Build test suite buildTests :: Bool buildTests = True -- | Compile with debug messages debug :: Bool debug = True }}} Maybe this feature would also solve #778. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/836> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #806: cabal test should not concatenate test logs by default
by Hackage 05 Jan '12

05 Jan '12

#806: cabal test should not concatenate test logs by default ----------------------------+----------------------------------------------- Reporter: tibbe | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.10.1.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- At the moment `cabal test` concatenates the human readable test logs by default. I don't find this very useful and makes the logs look like there's a bug in Cabal. I suggest that we don't append the logs by default (if ever). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/806> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 5

[Hackage] #845: [patch] Distribution/Compat/TempFile.hs: add dash separator before pid for createTempDirectory and openBinaryTempFile
by Hackage 05 Jan '12

05 Jan '12

#845: [patch] Distribution/Compat/TempFile.hs: add dash separator before pid for createTempDirectory and openBinaryTempFile ----------------------------+----------------------------------------------- Reporter: juhp | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- This patch just adds a '-' separator before pid when creating a temp directory or binary-file. So we get /tmp/mypkg-version/mypkg-version-pid/ instead of /tmp/mypkg-version/mypkg-versionpid/, which makes it much easier to pick out the version number. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/845> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #787: --test-option should support template argument
by Hackage 05 Jan '12

05 Jan '12

#787: --test-option should support template argument ----------------------------------+----------------------------------------- Reporter: tibbe | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: HEAD Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: Platform: | ----------------------------------+----------------------------------------- The test-framework package can optionally output JUnit XML, an XML flavor understood by many continuous build systems, if you pass it the `--jxml` flag. Using that flag, one can get `cabal test` to output JUnit XML: {{{ cabal configure --enable-tests cabal build cabal test --test-option=--jxml=dist/test/junit.xml }}} However, the `--test-option` flag doesn't allow the user to pass different flags to different test executables so each test executable will override the output of the previous. If the `--test-option` flag took a name template argument, supporting a `$test-suite` placeholder, you could generate one JUnit XML file per test suite: {{{ cabal configure --enable-tests cabal build cabal test --test-option=--jxml=dist/test/$test-suite.xml }}} The detailed test interface might support this in some nicer way, but this is a cheap way to have Cabal cooperate better with other test runners. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/787> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 5

[Hackage] #843: 'cabal test' crashes on Windows
by Hackage 05 Jan '12

05 Jan '12

#843: 'cabal test' crashes on Windows ----------------------------+----------------------------------------------- Reporter: ttuegel | Owner: ttuegel Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.10.1.0 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: Windows | ----------------------------+----------------------------------------------- Cabal crashes with the following error on Windows Vista and 7 (I have not tried XP): {{{ Running 1 test suites... Test suite tests: RUNNING... Test suite tests: PASS Test suite logged to: dist\test\foo-0.1-tests.log cabal: permission denied }}} The "permission denied" error appears to be from an attempt to delete a temporary file while it is still open. This does not appear to cause problems on Unix, but Windows won't allow it. I believe it is due to the fact that the temporary log file is read lazily, so it doesn't get closed before the file is deleted. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/843> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #839: hackage: produce haddock documentation for executable only projects as well
by Hackage 05 Jan '12

05 Jan '12

#839: hackage: produce haddock documentation for executable only projects as well --------------------------------+------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | --------------------------------+------------------------------------------- Hackage currently only contains haddock documentation for "libraries". However, it'd be really cool to be able to see the source code of "executable" only projects as well. If the project is not haddock'ized, then a simple hscolor'ed html source base would be fine as well (like in GitHub). One of the more common use cases of Hackage is to look at other people's code, even for projects that you wouldn't download. This can go along way in making that much more pleasurable. Alternatively, the user can specify a cabal flag to indicate if he wants browsable source code to be produced in case of executable only projects. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/839> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #779: Create tarball of all Hoogle input files
by Hackage 05 Jan '12

05 Jan '12

#779: Create tarball of all Hoogle input files --------------------------------+------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: HackageDB Component: hackageDB website | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | --------------------------------+------------------------------------------- For many packages on Hackage there is a corresponding Hoogle input file, for example: http://hackage.haskell.org/packages/archive/cmdargs/0.6.5/doc/html/cmdargs.… To generate Hoogle databases for every package on Hackage I have a script that downloads the documentation for every package, then puts it in a tarball and uploads it back to http://haskell.org/hoogle/hackage- haddock.tar.gz There are three disadvantages to the current process. It's quite a lot of connections to Hackage to download every single file, it takes quite a lot of time to download them individually (about 50 minutes using wget serially), and the tarball on Hoogle is often (always?) out of date. Would it be possible for Hackage to supply a tarball of all the Hoogle input files? -- Neil Mitchell (Hoogle author) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/779> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 8

[Hackage] #792: sdist doesn't not include source files from test-suite stanzas
by Hackage 05 Jan '12

05 Jan '12

#792: sdist doesn't not include source files from test-suite stanzas ----------------------------+----------------------------------------------- Reporter: tibbe | Owner: ttuegel Type: defect | Status: new Priority: normal | Milestone: Cabal-1.10 Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- `cabal sdist` doesn't include the source files from test-suite stanzas when generating the tarball. This leads to Hackage's QA checks rejecting the package. Steps to reproduce: 1. Create a Cabal package with a test-suite stanza (and set `hs-source- dirs` to e.g. `tests`). 2. Run `cabal sdist` 3. Unpack the tarball and look at the content. Thomas, could you please take a look? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/792> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 8

[Hackage] #735: cabal haddock --executables --hyperlink-source does not call HsColour
by Hackage 05 Jan '12

05 Jan '12

#735: cabal haddock --executables --hyperlink-source does not call HsColour ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ I am using "cabal haddock --executables --hyperlink-source" and this generates the API docs for all modules, and all have source links, but the actual html-ized source is only generated for the main module, and missing for all others. Cf. discussion at http://article.gmane.org/gmane.comp.lang.haskell.cafe/78987 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/735> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2