haskell-stack

When I run stack upload I get an error: Environment variable GPG_TTY is not set (see man gpg-agent) Unable to find gpg2 or gpg executable The upload appears to succeed, but the error concerns me. What are the consequences of this error? Is there a way to avoid to suppress it? As per discussion in the comments the errors are due to stack trying to automatically GPG sign packages that are being uploaded as of version 1.1.0 . To my understanding this is a stack-specific feature (with no package signing built into cabal or hackage), and it can be disabled with --no-signature command line option to

I know this seems a duplicate to Could not find module `Yesod' , but unlike that user, ghc-pkg list does not show Yesod in its output on my computer, they didn't seem to be using stack (I am, and I'm not sure if that means I don't need to worry about ghc-pkg list ), and additionally, the answer (code) to that question did not help my situation. The Yesod Book has an example that I've been trying to get to work for several hours now. I'll reprint it here {-# LANGUAGE OverloadedStrings #-} {-# LANGUAGE QuasiQuotes #-} {-# LANGUAGE TemplateHaskell #-} {-# LANGUAGE TypeFamilies #-} import Yesod

I have installed a bunch of packages to the snapshot database. I would now like a local copy of their documentation (even better if it's with hyperlinked source ). Is there a way I can tell stack to run haddock on all of them? EDIT (copied from my answer): It seems that the obvious stack haddock package will install haddock for the package, so $ cd ~/.stack/snapshots/x86_64-linux/lts-3.0/7.10.2/doc $ stack haddock * seems to do what I want, with two downsides: I'll still need to remember to pass the --haddock flag to every build (there isn't a ~/.stack/config file, is there?) It seems to

How to build an specific stack executable file, ie. those specified in projectname.cabal , like: executable executable-name hs-source-dirs: tools main-is: ExecutableModule.hs ghc-options: -Wall -threaded -rtsopts -with-rtsopts=-N build-depends: base , hsass , hlibsass I would need to compile executable-name and no other. It would be something like: stack build --executable executable-name Stack uses a component based lookup , e.g. stack build packagename:component-type:component-name So if your package is called "foo", and your executable is called "bar", you can use stack build foo:exe:bar

I am little confused about why this doesn't work. I have a small program that import System.Directory. When I run it with runhaskell on the command line it compiles and outputs what I expect. When I use the same program with stack I get a message saying Failed to load interface for ‘System.Directory’ It is a member of the hidden package ‘directory-1.3.0.0’. Use -v to see a list of the files searched for. I dont understand why it would work with runhaskell but not when i use stack ghci With the information you give, I can only attempt a guess… I think you have directory (globally) installed