The build artefacts of new-* are placed in a "dist-newstyle" directory.
Another common mistake with 1.24.0.0 is that `cabal new-build` won't
do much at all if run in some parent directory. You might need to
`cabal new-build ./my-blog/` and then get the artefacts somewhere
(burried) in
On 24/10/15 15:05, Thomas Tuegel wrote:
> MIN_VERSION_base is defined by Cabal, so it is not available during
> bootstrapping. This means we unfortunately need to use
> __GLASGOW_HASKELL__ in Cabal, even though it isn't really the right
> macro. It should be safe to use MIN_VERSION_base in
to the original reporter, making it less likely that the original
reporter would step up with more information if needed, etc.
On Tue, Feb 24, 2015 at 11:12 PM, Thomas Tuegel ttue...@gmail.com wrote:
On Tue, Feb 24, 2015 at 3:52 PM, lennart spitzner
l...@informatik.uni-kiel.de wrote:
hi,
i
hi,
i noticed today's run at the closing inactive issues on the tracker. i would
like to to ask an innocent question: what exactly is the benefit of this action?
(i disclose that it seems to me that valid, if inactive, issues are being
closed, which i do not like. but before complaining, i want
hello cabal devs,
i am willing to put a bit of time into improving the help texts of
cabal-install. some questions:
1) nobody else is working on this, right? is there risk that it
interferes with other's work? (i'd basically touch
Distribution.Simple.Command and the different fooCommand's in
