build-reports: option is invalid in a config file #405

Closed
bos opened this Issue May 24, 2012 · 4 comments

Comments

Projects
None yet
3 participants
@bos
Contributor

bos commented May 24, 2012

(Imported from Trac #412, reported by guest on 2008-11-22)

With darcs (tonight) cabal and cabal-install, I see the generated .cabal/config includes the line '-- build-reports:', suggesting that this is a valid configuration option.

However, it is not. If one uncomments it to 'build-reports: True', then Cabal warns and apparently ignores one's configuration as corrupt:

gwern@craft:29302~>cabal update
Warning: Error parsing config file /home/gwern/.cabal/config:9: "True"
Warning: Using default configuration.
Downloading package list from server
'http://hackage.haskell.org/packages/archive'

The syntax is valid, the True is correct, it's not listed as being part of a section. further, --build-reports is a valid CLI option:

gwern@craft:29304~>rm .cabal/config && mv config .cabal && cabal install --build-reports ztail [ 9:21PM]
Resolving dependencies...
Downloading hinotify-0.2...
[1 of 1] Compiling Main ( /tmp/TMPhinotify-0.2/hinotify-0.2/Setup.lhs, /tmp/TMPhinotify-0.2/hinotify-0.2/dist/setup/Main.o )
Linking /tmp/TMPhinotify-0.2/hinotify-0.2/dist/setup/setup ...
Downloading ztail-1.0...
........

Either the default config is lying/wrong, or the build-reports: option is busted.

@bos

This comment has been minimized.

Show comment Hide comment
@bos

bos May 24, 2012

Contributor

(Imported comment by @dcoutts on 2008-11-22)

See also #368.

Contributor

bos commented May 24, 2012

(Imported comment by @dcoutts on 2008-11-22)

See also #368.

@bos

This comment has been minimized.

Show comment Hide comment
@bos

bos May 24, 2012

Contributor

(Imported comment by @kosmikus on 2009-01-26)

I think there's no longer a build-report option being generated in the config file. But certainly #368 is still a problem, so keeping this one around, too, for now.

Contributor

bos commented May 24, 2012

(Imported comment by @kosmikus on 2009-01-26)

I think there's no longer a build-report option being generated in the config file. But certainly #368 is still a problem, so keeping this one around, too, for now.

@bos

This comment has been minimized.

Show comment Hide comment
@bos

bos May 24, 2012

Contributor

(Imported comment by @kosmikus on 2012-03-06)

Duncan says: "Right. There is a 'remote-build-reporting' field and that's broken for
other reasons :-("

So I'm leaving this open, but moving it to a later release.

Contributor

bos commented May 24, 2012

(Imported comment by @kosmikus on 2012-03-06)

Duncan says: "Right. There is a 'remote-build-reporting' field and that's broken for
other reasons :-("

So I'm leaving this open, but moving it to a later release.

@BardurArantsson

This comment has been minimized.

Show comment Hide comment
@BardurArantsson

BardurArantsson Jun 25, 2015

Collaborator

This is obsolete. Please close.

Collaborator

BardurArantsson commented Jun 25, 2015

This is obsolete. Please close.

@23Skidoo 23Skidoo closed this Jun 26, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment