GSoC 2022 for Stack

Hey all, Jasper Van der Jeugt sent me a message about GSoC. If anyone is interested in participating on behalf of Stack this year, either as a mentor or a student, please let me know and I'll connect you with Jasper. I've sent similar messages on the Haskell Foundation channels

Re: Can't open `libgmp.so.10` when using `stack build`

I have no experience with Manjaro, so I'm not sure exactly may be happening here. Perhaps setting LD_LIBRARY_PATH to the dir that contains the .so may help? On Sun, Apr 18, 2021, at 9:17 AM, Noah G. wrote: > Hi all, > > I am trying to use Stack on Manjaro 21.0.1 Ornara. When I run stack build,

Re: Can the GHC LLVM backend be used "universally" with Stack?

I don't personally know anything about this, I've never really used the LLVM backend or related tools. Maybe others have some experience with this. On Fri, Apr 16, 2021, at 10:12 PM, Howard B. Golden wrote: > Hi, > > Is it possible to install and use a version of Stack where everything (e.g.,

Re: GSoC 2021

Designing a solution is definitely part of the project here. We don't have a complete solution in mind yet. I'm sure plenty of people-myself included-would be happy to provide some feedback and thoughts on what it should look like. Expected skills really just come down to the ability to work on

Stack Governance

I’ve written up an initial proposal and a call for participants in my most recent blog post: https://www.snoyman.com/blog/2021/01/stack-governance/ I’m cross-posting this to multiple areas, since there isn’t an official discussion area determined yet. -- You received this message because you

Re: How to satisfy Hackage uploading Stack-based packages

On Wed, Dec 9, 2020 at 5:33 PM sshuck wrote: > Fantastic, thanks for the quick reply, digging in, and the suggestions. > > Just to get over the hump, I did two more releases, the first manually > relaxing the text lower bound (failed), and the second removing > --pvp-bounds altogether

Re: How to satisfy Hackage uploading Stack-based packages

You can see the cabal build error by clicking on the "build log" link on your Hackage page, which goes to https://hackage.haskell.org/package/pcre2-1.0.0/reports/2. Here's the juicy bit: [__1] rejecting: text-1.2.3.2/installed-1.2.3.2 (conflict: pcre2 => text>=1.2.4.0 && <1.3) [__1] trying:

Re: How to ghc "Finding imports" on stack

You can use source-dirs (in hpack/package.yaml) or hs-source-dirs (in cabal files) to specify the directory. Though standard practice these days in Haskell projects is to put the code in an src directory. For more information on hpack settings and some examples, check out:

Platform support for Stack 2.3 release

Hi all, For the upcoming 2.3 release of Stack, we're going to be reducing the number of platforms that we support with binary releases. The reason behind this is that we've been slowed down in our release process until now with issues trying to build binaries for less common platforms. In order

Re: Generating fully resolved snapshots

mes a need of our own. > > On Wed, Apr 1, 2020 at 7:10 PM Alexander Bondarenko > wrote: > > > > Thanks! This would be most helpful. > > > > On Wednesday, April 1, 2020 at 11:55:44 AM UTC+3, Michael Snoyman wrote: > >> > >> Thanks for raising this befor

Re: Generating fully resolved snapshots

Thanks for raising this before the release :) The functionality for adding complete package information to a snapshot file lives in the pantry package, not in Stack. I think I'd like to go in the direction of exposing this functionality via Pantry instead of Stack, since I don't want to add the

Re: I am not able to use stack

version of ghc. It is > interesting, but new versions of sbcl always work with older programs. Does > Haskell need old compiler versions for older programs? It seems that there > is no effort to keep backward compatibility. > > > Em ter, 23 de jul de 2019 às 11:06, Mic

Re: I am not able to use stack

yi is not present in recent Stackage snapshots. I'm not particularly fond of Stack's behavior in this case; I'd rather it be more explicit about adding packages outside of a snapshot. In any event, if you check out the yi page on stackage.org[1], you can see that the last snapshot to include yi is

mirrors.json is expired

Currently, the mirrors.json file on Hackage is expired, which may cause issues for Stack users, especially for first time users trying to download the package index. There's a full explanation and a workaround available at: https://github.com/commercialhaskell/stack/issues/4928 Even if you're

Re: Stack 2 release plans

; How can we migrate? > > 2019年4月25日(木) 12:36 Michael Snoyman : > >> I've published a blog post with plans for changes to Stackage and the >> release of Stack 2. There are some big changes in Stack 2, so I'd strongly >> encourage users to do some testing before relea

Stack 2 release plans

I've published a blog post with plans for changes to Stackage and the release of Stack 2. There are some big changes in Stack 2, so I'd strongly encourage users to do some testing before release to see if any workflows have been significantly impacted. -- You received this message because you

STACK_LOCK lockfile support in Stack

Hi all, There's a feature which has been available in Stack for a while now: respecting a `STACK_LOCK` environment variable to cause some locking to occur while using Stack. This feature is off by default, and I don't believe is very well documented. I'm also uncertain if it's used at all,

Re: Create docker

I use Docker extensively in Haskell projects, both for builds and deployments. We do this for most work at FP Complete as well, and most of our clients do too. The issue you're running into is that you're using a Haskell _build_ image (which includes GHC and other build tools) for creating a

Re: High CPU usage on Mac OS

orkaround? > Because, I cannot for sure continue like this...! > > Thanks in advance! > > Τη Κυριακή, 20 Ιανουαρίου 2019 - 7:03:56 μ.μ. UTC+1, ο χρήστης Michael > Snoyman έγραψε: >> >> If it's high with both cabal and stack, it's most likely the compilation >>

Re: High CPU usage on Mac OS

If it's high with both cabal and stack, it's most likely the compilation with GHC itself. The best way to check would be to open up Activity Monitor, turn to the CPU tab, sort by CPU usage descending, and then start compiling. The culprit should be readily apparent. On Sat, Jan 19, 2019 at 7:25

Re: Proposal: Stack Code of Conduct

Thanks for bringing it up. We're having a bit of a discussion over on the issue tracker about it: https://github.com/snoyberg/stack-coc/pull/3#issuecomment-437085367 On Fri, Nov 9, 2018, 1:34 AM Magnus Therning On Wed, 7 Nov 2018 at 08:47, Michael Snoyman wrote: > > > > I've put tog

Proposal: Stack Code of Conduct

I've put together a blog post outlining some thoughts around an unofficial code of conduct: https://www.snoyman.com/blog/2018/11/proposal-stack-coc If you're interested, please also see the Github repo:

Re: Ask stack for local filepath of downloaded repo after compilation

eady 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, 2018 at 1:08 PM Michael Snoyman <mailto:mich...@sn

Re: Ask stack for local filepath of downloaded repo after compilation

I think this is too abstract a question to know how to answer it. What questions do you want to ask? Also, most of the usage of that directory will be changing drastically in the next release of Stack due to the introduction of pantry, which handles downloaded packages more efficiently. > On

Re: Windows error with LTS 12.6

Running stack upgrade should be sufficient. On Sun, Aug 19, 2018, 9:33 PM aditya siram wrote: > The offending line in bhoogle-0.1.3.4's Cabal file is: > > license: BSD-3-Clause OR Apache-2.0 > > > > On Sunday, August 19, 2018 at 11:20:27 AM UTC-7, aditya siram wrote: >> >> I just

Re: Can't build cassava (for csv file I/O) (my first attempt to use stack to build something useful)

What version of Stack are you using? What message do you get if you remove the entire extra-deps section? On Sun, Aug 12, 2018, 6:07 AM Jack Vice wrote: > I am trying to import .csv data and so I am trying to build a simple > example using cassava and I have run out of ideas to get it to work.

Re: stack setup ExitFailure 2 installing ghc os Mac OS High Sierra

ne, ready to 'make > install' > @(src/Stack/Setup.hs:1097:54) > 2018-08-05 02:39:51.247017: [debug] (see README and INSTALL files for > more info.) > @(src/Stack/Setup.hs:1097:54) > 2018-08-05 02:39:51.247327: [debug] > > @

Re: stack setup ExitFailure 2 installing ghc os Mac OS High Sierra

Please rerun with --verbose to get more information on how it's failing. On Sun, Aug 5, 2018, 12:54 AM Bryan Dunphy wrote: > stack --version > > Version 1.7.1, Git revision 681c800873816c022739ca7ed14755e85a579565 (5807 > commits) x86_64 hpack-0.28.2 > > > > message is: > > > stack build > >

Re: unrecognized 'configure' option `--with-hpack=

com> wrote: > Thank you for responding. > > A minimal project can be found on https://github.com/ > MuratOzsoyler/stack-with-hpack-problem. README explains extensively how > to reproduce the problem. > > Thanks in advance for your kind help. > > 17 Nis 2018 Sal, 09:51

Re: 'stack build' fails; can't seem to copy over file.

Does the directory C:\sr\snapshots\9f8b1558\doc exist? Are you able to manually create files in it? On Mon, Mar 19, 2018 at 9:13 PM, Lance Clark <hayn...@gmail.com> wrote: > Here’s the output for that: http://pastebin.com/1Kdz3NHX > > On Mar 19, 2018, at 01:06, Michae

Stack patching policy

I've written up a blog post about a policy change in handling patches to upstream dependencies: https://www.snoyman.com/blog/2018/02/stack-patching-policy This will in particular impact those packaging Stack, such as Linux distro package maintainers. There's a designated Github issue for

Re: Using stack to provide a consistent build environment for something that is not a cabal package?

IIUC, you're looking to define a `stack.yaml` file which will set up all of the packages and settings, and then have a script you run to tell Stack to build the appropriate packages. That sounds fine; I think the pieces you're missing are: * In order to say "I have no local packages," include the

Dropped packages following LTS 10

Copied from: https://www.snoyman.com/blog/2017/12/dropped-packages-following-lts-10 tl;dr: Check this pull request to see if your package was just removed from Stackage Nightly. Stackage Nightly maintains a set of upper bounds to give package

Re: get source code by module name

I can't think of an easy way to do it. It will come down to: * Looking up which package the module came from (likely in the GHC package database) * Figuring out if it's in the snapshot or local (the `stack query` command may help here) * Finding the relevant source code, checking hs-source-dirs

Re: Problems with custom snapshots

n Thu, Dec 7, 2017 at 10:12 PM, Michael Snoyman < > michael.snoy...@gmail.com> wrote: > >> I know this bug :(. It's an old Cabal bug, where build-depends for >> non-buildable components are still required. When dealing with older Cabal >> libraries, we need to make sure thos

Re: Problems with custom snapshots

I know this bug :(. It's an old Cabal bug, where build-depends for non-buildable components are still required. When dealing with older Cabal libraries, we need to make sure those libraries are available, even though they aren't needed. This isn't custom snapshot specific, you can reproduce by

Re: Win32 binary disappeared

I believe there are plans to release it still. As the release announcement mentioned, we didn't complete the normal release procedure to rush the fix for GHC 8.2, and some binaries are still being compiled. On Thu, Dec 7, 2017 at 2:13 PM, Neil Mitchell wrote: > Hi, > > The

Re: Plugin support

so can’t link to them. > > I don’t understand either gitit’s source code or stack’s > philosophy/intent, so have no idea what the correct solution is. > > — Perry > > > On Oct 17, 2017, at 1:52 AM, Michael Snoyman <michael.snoy...@gmail.com> > wrote: > > I can't spe

Re: Native, non-haskell libraries in stack, cabal, haskell

On Tue, Oct 17, 2017 at 3:15 PM, Nehal Patel wrote: > Hi -- I'm new to stack, haskell, etc and I am confused about how to reason > about build repeatability when consuming packages that rely on "native, > non-haskell libraries" (e.g. libcairo). > > * Is it the case that

Additional group moderators

Hi all, This mailing list is moderated to avoid spam. I've been doing most of the approvals for first time submitters, but it would be nice to have a few others on the team in case I'm unavailable. The workload here is _really_ small: 5-10 minutes a week tops. The basic idea is: * Get a

Re: Plugin support

I can't speak for others, but from this email I don't understand what the question is. I'm personally not familiar with the plugin mechanism provided by Gitit. Perhaps you can provide a little more detail? On Sat, Oct 14, 2017 at 3:25 AM, Perry Wagle wrote: > Gitit is a wiki

Re: libgmp in non-standard location

I'm not expert on this, but I believe you'll need to set LD_CONFIG appropriately instead of using --extra-lib-dirs. The --extra-lib-dirs is not used during GHC sanity check if I remember correctly. On Sun, Jul 23, 2017 at 11:56 PM, Jan von Löwenstein < jan.loewenst...@gmail.com> wrote: > Hi, > >

Re: Why is stack not using the home directory on Windows?

How did you install Stack? Do you possibly have the STACK_ROOT environment variable set? On Wed, Jul 19, 2017, 2:58 PM Hristo Hristov wrote: > Hello > > On Windows stack is downloading stuff to the root drive C:\sr\config.yaml > > Why isn't stack using %LOCALAPPDATA% or any

Re: Extensible snapshots & local paths

e to include 1.4.0, the source and dependencies of > master. Could turn out I would not safe a bit right now. > > Anyway, great to see extensible snapshots will come and will include the > possibility to ship dependencies as tarballs. > > Michael Snoyman <michael.snoy...@gmail.com&

Re: Extensible snapshots & local paths

t to play with a version build from master > soon. Any idea when the next release is planned? > > 1.4.0 was released in March, wasn't it? Release before that was December. > Not sure if that already makes a three month release schedule... ;) > > Michael Snoyman <michael.snoy...@gmail

Re: Extensible snapshots & local paths

t Haskell based project and while I think I learned a lot since > November last year there is still so many things ahead... > > Best > Jan > > Michael Snoyman <michael.snoy...@gmail.com> schrieb am Sa., 15. Juli > 2017, 20:23: > >> On mobile, apologies for brevity.

Re: Extensible snapshots & local paths

On mobile, apologies for brevity. Your use case makes sense. I can think of two workarounds. 1. Allow an explicit opt in to say "allow file paths, I know what I'm doing" 2. Support local tarballs, especially if we include a sha256 of the tarball contents (a feature I'm planning to add next

Enable --install-ghc by default?

I've received a request from the Haskell website working group to make a modification to Stack to simplify the new user onboarding process. Specifically: change the default behavior to --install-ghc, meaning that if you run a command like `stack build` and the appropriate GHC is not installed, it

Re: stack setup fails with libgmp in nonstandard location

Does setting LD_LIBRARY_PATH fix the problem? On Fri, Jun 2, 2017 at 5:37 PM, 'Stephan Schiffels' via haskell-stack < haskell-stack@googlegroups.com> wrote: > Sorry, but does someone know any help here? > > Am Dienstag, 11. April 2017 21:18:52 UTC+2 schrieb Stephan Schiffels: >> >> Hi, I am

Re: Compiling a shared (DLL) library with stack

I can only speak for myself here, but generating Windows DLLs is simply uncharted waters (whether with or without Stack). I'm not sure if anyone else has given this a shot before either. On Thu, Mar 23, 2017 at 11:32 AM, wrote: > Hello all, > > first of all - my thanks to

Git-based package index support

Stack includes support for getting package indices (the collection of packages and their cabal files) from both an HTTP-downloaded tarball and a Git repository. Up until the most recent release of Stack, the default package index used the all-cabal-hashes repo[1]. As I detailed in a recent blog

Re: -exe in name of executable

Just remove the -exe in the .cabal file. You can name the file whatever you want there. On Wed, Nov 23, 2016 at 12:37 PM, kees Bleijenberg < k.bleijenb...@lijbrandt.nl> wrote: > If I do 'stack build' stack builds the executable X-exe.exe. > Why is that -exe in the name? How do I let stack

Re: stack install to get the latest executable from hackage?

Actually, you probably want to stick to the second one to avoid dependency problems. On Fri, Nov 18, 2016, 2:19 PM Michael Snoyman <mich...@snoyman.com> wrote: > stack install cabal-install-1.24.1.0 > > Or > > stack --resolver nightly --install-ghc install cabal-install >

Re: Logo

I'm not aware of any official _or_ unofficial logo for Stack yet. Is anyone out there interested in creating one? On Wed, Sep 28, 2016 at 4:57 PM, Leander Kurscheidt < leander.kursche...@gmail.com> wrote: > I am currently working on a patch where the problem arises that we need to > communicate

Re: Simplifying the travis CI .travis.yml file instructions?

I wasn't actually aware of that separate page. I always just copy the content out of the guide from: https://docs.haskellstack.org/en/stable/GUIDE/#travis-with-caching I'd be in favor also of simplifying the story here, but perhaps others who have been involved with putting these docs together