forth. A deep dive
into using shake pervasively may prove beneficial, although I have
practically no experience with shake so I could be completely off base here.
-- Dan Burton
On Mon, Jul 11, 2016 at 9:55 AM, Michael Sloan wrote:
> Yeah, one thing I've wanted shake integration for is
aving the verbose default is fine, but my personal preference is to only
put something in stack.yaml if it deviates from the default.
-- Dan Burton
On Tue, Aug 30, 2016 at 12:18 PM, Harendra Kumar
wrote:
> The comments provide new users (and sometimes even to experienced ones) a
> hand
Yes, .stack-work is a folder that should definitely be gitignored
-- Dan Burton
On Tue, Oct 4, 2016 at 1:45 PM, Ryo Ota wrote:
> I'd like to minimize a project to commit or push git/Github.
> In addition, I'd like to create a repository which has a reproducibility.
> It me
p, send email to haskell-stack@googlegroups.com
> .
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/haskell-stack/5db29a15-bc7b-48a4-93dd-86e51de9af48%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/haskell-stack/5db29a15-bc7b-48a4-93dd-86e51d
Things to try:
* update the "resolver" field in /root/.stack/global-project/stack.yaml to
lts-7.14
If that doesn't work, you can try the nuclear option:
* delete everything in /root/.stack/snapshots
-- Dan Burton
On Mon, Dec 26, 2016 at 2:25 AM, yu ming wrote:
> i ran &quo
are only using stack to build your project, then you can safely delete the
cabal.config.
-- Dan Burton
On Tue, May 16, 2017 at 5:02 AM, Adam Bergmark wrote:
> When using stack you simply refer to a snapshot by name, it essentially
> contains the same information as this cabal.config (while
Does Intero not have a feature like this already?
It seems like we have all the info available to at least provide this as a
web service for in-snapshot packages. The module-to-package relation is 1
to 1 most of the time.
On Dec 19, 2017 6:57 AM, "Michael Snoyman"
wrote:
> I can't think of an e
/cc the haskell-stack mailing list.
On Dec 24, 2017 9:08 AM, "Eric McCorkle" wrote:
> Hi folks,
>
> I'm trying to update my language project to happy >= 9.16, so I can use
> typeclass-based parsers. Unfortunately, I'm running into build errors
> after switching to lts-9.20. The log file is att
t on this issue?
-- Dan Burton
On Thu, May 24, 2018 at 7:34 AM, Thomas Løcke
wrote:
> Hi Simon
>
> The newest GHC I can get with my system package manager is 7.10.3, so
> sadly not a solution.
>
>
> Den tor. 24. maj 2018 kl. 16.18 skrev 'Simon Jakobi' via ha
p. if stack has
downloaded multiple commits from this repo over time.)
If this cannot already be done with the existing CLI, perhaps it would be
worthwhile to open a feature request. It seems like the sort of capability
one might expect to find under `stack path`.
-- Dan Burton
On Sat, Oct 20,
What exactly is the problem?
When I do this:
stack unpack stack-2.3.1 && cd stack-2.3.1
echo 'resolver: nightly-2020-08-03' > stack.yaml
stack build --dry-run
It constructs a valid build plan using ghc 8.10 for building stack-2.3.1
which includes the latest pantry and
I tried the build and it seems that stack-2.3.1 has a build failure with
pantry-0.5.1.1 due to src/Stack/Types/Resolver being duplicated in both.
-- Dan Burton
On Wed, Aug 5, 2020 at 11:39 AM Gleb Popov <6year...@gmail.com> wrote:
>
>
> On Wednesday, August 5, 2020 at 7:37:49
I'm not sure what the planned release schedule is, but the patch _should_
be fairly simple if that's the way you want to go.
-- Dan Burton
On Wed, Aug 5, 2020 at 1:12 PM Gleb Popov <6year...@gmail.com> wrote:
>
>
> On Wednesday, August 5, 2020 at 8:31:20 PM UTC+4 dan
13 matches
Mail list logo
