September 2007 - cabal-devel

patch applied (cabal): Correct the verbosity range in the "--help" text
by Duncan Coutts 20 Sep '07

20 Sep '07

Sun Sep 16 19:44:16 PDT 2007 Duncan Coutts <duncan(a)haskell.org> * Correct the verbosity range in the "--help" text The correct range in 0--3, not 0--2 or 0--5 M ./Distribution/Simple/Setup.hs -1 +1 M ./Distribution/Simple/SetupWrapper.hs -1 +2

1 0

Re: cpphs and C++-style comments
by Malcolm Wallace 19 Sep '07

19 Sep '07

Benjamin Franksen <benjamin.franksen(a)bessy.de> wrote: > > OK, done. The new option name is --strip-eol, and --strip-c89 is > > gone. > > I'd rather name the flag --strip-cc or something like that, indicating > that it refers to C++ comments (--strip-cpp might be misleading, though). How about --strip-c++ then? Regards, Malcolm

1 0

[Hackage] #156: setup haddock: option to expose all modules
by Hackage 17 Sep '07

17 Sep '07

#156: setup haddock: option to expose all modules ----------------------------------+----------------------------------------- Reporter: ross(a)soi.city.ac.uk | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal | Version: 1.2.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.6 Platform: Linux | ----------------------------------+----------------------------------------- (Requested by g9ks157k(a)acme.softbase.org) If I want to build a documentation for developers which exposes all private things, it is not enough to run Haddock with `--ignore-all- exports`. Cabal already runs haddock over all the modules, but it adds `--hide` options for modules that are not exposed. Could there be an option to turn this off, so that all modules appear in the documentation? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/156> Hackage <http://example.com/> My example project

1 1

Re: [Hackage] #104: "setup install" should configure and build if necessary
by Hackage 17 Sep '07

17 Sep '07

#104: "setup install" should configure and build if necessary --------------------------+------------------------------------------------- Reporter: guest | Owner: ijones Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal | Version: 1.1.6 Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.4.2 | Platform: Linux --------------------------+------------------------------------------------- Changes (by ross(a)soi.city.ac.uk) * difficulty: easy (<4 hours) => normal * type: task => enhancement -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/104> Hackage <http://example.com/> My example project

1 0

Re: [Hackage] #125: running Haddock with different options not possible
by Hackage 17 Sep '07

17 Sep '07

#125: running Haddock with different options not possible -----------------------------------------+---------------------------------- Reporter: g9ks157k(a)acme.softbase.org | Owner: ijones Type: enhancement | Status: closed Priority: normal | Milestone: Component: Cabal | Version: 1.1.6 Severity: normal | Resolution: fixed Keywords: | Difficulty: normal Ghcversion: 6.6 | Platform: Linux -----------------------------------------+---------------------------------- Changes (by ross(a)soi.city.ac.uk) * resolution: => fixed * status: new => closed Comment: new request opened as #156 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/125> Hackage <http://example.com/> My example project

1 0

Re: [Hackage] #125: running Haddock with different options not possible
by Hackage 17 Sep '07

17 Sep '07

#125: running Haddock with different options not possible -----------------------------------------+---------------------------------- Reporter: g9ks157k(a)acme.softbase.org | Owner: ijones Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal | Version: 1.1.6 Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.6 | Platform: Linux -----------------------------------------+---------------------------------- Comment (by duncan): So can we open a new bug for that feature request and close this bug now? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/125> Hackage <http://example.com/> My example project

1 0

Re: [Hackage] #125: running Haddock with different options not possible
by Hackage 17 Sep '07

17 Sep '07

#125: running Haddock with different options not possible -----------------------------------------+---------------------------------- Reporter: g9ks157k(a)acme.softbase.org | Owner: ijones Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal | Version: 1.1.6 Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.6 | Platform: Linux -----------------------------------------+---------------------------------- Comment (by ross(a)soi.city.ac.uk) Cabal already runs haddock over all the modules, but it adds --hide options for the other modules. It would certainly be possible to add an option to turn that off. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/125> Hackage <http://example.com/> My example project

1 0

Re: [Hackage] #125: running Haddock with different options not possible
by Hackage 17 Sep '07

17 Sep '07

#125: running Haddock with different options not possible -----------------------------------------+---------------------------------- Reporter: g9ks157k(a)acme.softbase.org | Owner: ijones Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal | Version: 1.1.6 Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.6 | Platform: Linux -----------------------------------------+---------------------------------- Comment (by g9ks157k(a)acme.softbase.org) This does help, indeed. However, there is a related problem. If I want to build a documentation for developers which exposes all private things, it is not enough to run Haddock with {{{--ignore-all-exports}}}. Cabal has to run Haddock on all modules of the package, not just the modules which are exposed. Could such a feature be implemented as well? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/125> Hackage <http://example.com/> My example project

1 0

[Hackage] #154: Cabal doesn't clean "_stub" files
by Hackage 17 Sep '07

17 Sep '07

#154: Cabal doesn't clean "_stub" files ---------------------+------------------------------------------------------ Reporter: judahj | Owner: Type: defect | Status: new Priority: normal | Milestone: Cabal-1.2 Component: Cabal | Version: 1.2.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.6 Platform: Mac OS | ---------------------+------------------------------------------------------ Running "runhaskell Setup.hs clean" doesn't clean _stub.{c,h} files in Cabal-1.2.0. It does in 1.1.6.2. The -stubdir flag might be useful here (introduced in ghc-6.6) for having them created in the dist/build directory. (In both 1.2.0 and 1.1.6.2, they're created next to the source .hs files.) Related: [542]. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/154> Hackage <http://example.com/> My example project

1 1

patch applied (cabal): look in odir for source and .hs files, not buildDir lbi
by Duncan Coutts 17 Sep '07

17 Sep '07

Mon Sep 17 07:50:30 PDT 2007 Duncan Coutts <duncan(a)haskell.org> * look in odir for source and .hs files, not buildDir lbi odir = buildDir lbi for the lib case, which is why it worked most of the time in testing but in the exe case it's a different dir. M ./Distribution/Simple/GHC.hs -2 +2

1 0