- cabal-devel - Haskell.org

Re: [Hackage] #223: allow per-package configuration options in config file
by Hackage 03 Mar '12

03 Mar '12

#223: allow per-package configuration options in config file ----------------------------------+----------------------------------------- Reporter: duncan | Owner: mnislaih Type: enhancement | Status: assigned Priority: normal | Milestone: Cabal-1.16 Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: 6.8.2 Platform: | ----------------------------------+----------------------------------------- Changes (by kosmikus): * milestone: => Cabal-1.16 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/223#comment:9> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #446: Can't set path to tools in ~/.cabal/config
by Hackage 03 Mar '12

03 Mar '12

#446: Can't set path to tools in ~/.cabal/config ---------------------------------+------------------------------------------ Reporter: awick | Owner: Type: defect | Status: new Priority: normal | Milestone: cabal-install-0.16 Component: cabal-install tool | Version: HEAD Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: | ---------------------------------+------------------------------------------ Changes (by kosmikus): * milestone: cabal-install-0.10 => cabal-install-0.16 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/446#comment:5> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #227: cabal-install doesn't consider build-tools as dependencies
by Hackage 02 Mar '12

02 Mar '12

#227: cabal-install doesn't consider build-tools as dependencies ---------------------------------+------------------------------------------ Reporter: guest | Owner: duncan Type: defect | Status: assigned Priority: normal | Milestone: cabal-install-0.16 Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Keywords: dependencies build tools Difficulty: hard (< 1 day) | Ghcversion: 6.12.3 Platform: | ---------------------------------+------------------------------------------ Changes (by kosmikus): * milestone: cabal-install-0.8 => cabal-install-0.16 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/227#comment:13> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #592: cabal test does not detect that cabal build needs to be re-run
by Hackage 02 Mar '12

02 Mar '12

#592: cabal test does not detect that cabal build needs to be re-run ----------------------------+----------------------------------------------- Reporter: kowey | Owner: ttuegel Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Comment(by tibbe): Could you make sure `cabal bench` also implies `cabal build` while you're at it? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/592#comment:7> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #592: cabal test does not detect that cabal build needs to be re-run
by Hackage 01 Mar '12

01 Mar '12

#592: cabal test does not detect that cabal build needs to be re-run ----------------------------+----------------------------------------------- Reporter: kowey | Owner: ttuegel Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Comment(by tibbe): Replying to [comment:5 ttuegel]: > We've discussed this before, and I think the conclusion we came to was that 'cabal test' should run 'cabal build' if necessary, but we should not change the behavior of './Setup test'. Is that still the consensus? Sounds good to me. > I'm not sure what was meant by "it becomes clear what needs to be rebuild because we actually have accurate information about it." Maybe this is naive, but I think if we simply call 'cabal build' before running 'cabal test', it will only rebuild what needs rebuilding. That is, I think all the checks we need are in place already. Am I missing something? Nope. Just run `cabal build` before. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/592#comment:6> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #592: cabal test does not detect that cabal build needs to be re-run
by Hackage 01 Mar '12

01 Mar '12

#592: cabal test does not detect that cabal build needs to be re-run ----------------------------+----------------------------------------------- Reporter: kowey | Owner: ttuegel Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Comment(by ttuegel): Replying to [comment:4 tibbe]: > We now have a test-suite section so this should be feasible to address. Thomas, what do you think? We've discussed this before, and I think the conclusion we came to was that 'cabal test' should run 'cabal build' if necessary, but we should not change the behavior of './Setup test'. Is that still the consensus? I'm not sure what was meant by "it becomes clear what needs to be rebuild because we actually have accurate information about it." Maybe this is naive, but I think if we simply call 'cabal build' before running 'cabal test', it will only rebuild what needs rebuilding. That is, I think all the checks we need are in place already. Am I missing something? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/592#comment:5> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #592: cabal test does not detect that cabal build needs to be re-run
by Hackage 29 Feb '12

29 Feb '12

#592: cabal test does not detect that cabal build needs to be re-run ----------------------------+----------------------------------------------- Reporter: kowey | Owner: ttuegel Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Changes (by tibbe): * cc: johan.tibell@… (added) * owner: => ttuegel Comment: We now have a test-suite section so this should be feasible to address. Thomas, what do you think? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/592#comment:4> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

[Hackage] #894: Add benchmark support
by Hackage 29 Feb '12

29 Feb '12

#894: Add benchmark support ----------------------------+----------------------------------------------- Reporter: tibbe | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Today, a user needs to rely on external tools, such as Make, to build benchmarks associated with a package. This has a couple of issues: * It's hard to have both Make (which builds the benchmark) and Cabal (which builds the library) pick the same versions of package dependencies. This leads to compilation errors when the user installs or removes some packages from his/her system. * It's hard to accurately track what needs to be rebuilt when, forcing the user to rebuild more than necessary, which wastes time. Proposal: Add a new `.cabal` file section for benchmarks, modeled after the "test-suite" section. Usage: {{{ cabal configure --enable-benchmarks cabal build cabal bench # results are written to stdout }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/894> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

cabal test seems broken with cabal-install HEAD
by Johan Tibell 24 Feb '12

24 Feb '12

Hi, I tried to use cabal-install from today's HEAD but it doesn't seem to pick up test-suites anymore: $ ../cabal/cabal-install/dist/build/cabal/cabal clean cleaning... $ ../cabal/cabal-install/dist/build/cabal/cabal configure --enable-tests --enable-library-coverage Resolving dependencies... Configuring hashable-1.1.2.3... $ ../cabal/cabal-install/dist/build/cabal/cabal build Building hashable-1.1.2.3... Preprocessing library hashable-1.1.2.3... [1 of 1] Compiling Data.Hashable ( Data/Hashable.hs, dist/build/Data/Hashable.o ) Registering hashable-1.1.2.3... $ ../cabal/cabal-install/dist/build/cabal/cabal test --test-option=--plain --test-option=--jxml=dist/unit-tests.xml cabal: No test suites enabled. Did you remember to configure with '--enable-tests'? This is using the hashable package from https://github.com/tibbe/hashable -- Johan

3 4

patch applied (hackage-server): "Add package tarball redirects for current cabal-install versions" and 1 others
by duncan＠lun.haskell.org 23 Feb '12

23 Feb '12

Thu Feb 23 14:19:17 GMT 2012 Duncan Coutts <duncan(a)community.haskell.org> * Add package tarball redirects for current cabal-install versions Ignore-this: 16df6b5c8b71e964a4177ed575b06984 They expect /package/foo-1.0.tar.gz rather than /package/foo-1.0/foo-1.0.tar.gz M ./Distribution/Server/Features/LegacyRedirects.hs -3 +13 Thu Feb 23 14:41:48 GMT 2012 Duncan Coutts <duncan(a)community.haskell.org> * Use the real hostname in the server startup message Ignore-this: 5e5c36c45d01de9735c0a8cd48be76b9 M ./Main.hs -1 +1

1 0