I'm not sure what you're saying your desired outcome is here. Are you planning on using the Haskell file I provided and compiling it yourself?
On Thu, Apr 2, 2020 at 7:34 PM IC Rainbow <ic.r...@gmail.com> wrote: > Now, having integrated snapshot resolver into my build I think making > it a standalone executable would be much better. > Pantry brings quite a few dependencies and grafting it unto Shake > build looks suboptimal. > And I worry about stack/pantry being buildable with latest and > greatest stackage snapshots. Tracking nightlies isn't a priority for > stack, but sometimes a need of our own. > > On Wed, Apr 1, 2020 at 7:10 PM Alexander Bondarenko <ic.r...@gmail.com> > 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 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 complexity back into Stack. Also, the > original reason for removing the freeze functionality was due to questions > of how to handle now-deprecated hpack-only packages. I'd rather not get > into that debate again, and leave that handling up to the caller. > >> > >> I've put together a Gist demonstrating how to complete a snapshot layer: > >> > >> https://gist.github.com/snoyberg/99849b2c92b1a34f0cd9c509e2161ab7 > >> > >> It includes a `foo.yaml` custom snapshot file, and a `Main.hs` which > uses that snapshot for running, and then generates a `bar.yaml` with the > package and snapshot information completed. I could imagine adding an > executable-maybe optional-to the pantry package to expose this > functionality. What do you think? > >> > >> On Tue, Mar 31, 2020 at 9:27 PM Alexander Bondarenko <ic....@gmail.com> > wrote: > >>> > >>> Hi! > >>> > >>> Stack 2.1.3 had "freeze --snapshot" command that put all "completed" > parts together with originals. The result then could be fed to "--resolver" > option removing the need to download stuff or update pantry db. > >>> This allows a read-only stack root which then can be shipped as a deb > package. > >>> > >>> With 2.3 removing the command one has to mess around lock files to > assemble the said snapshot. Are there any alternatives? Maybe bring back > snapshot generation as a standalone command? > >>> > >>> -- > >>> You received this message because you are subscribed to the Google > Groups "haskell-stack" group. > >>> To unsubscribe from this group and stop receiving emails from it, send > an email to haskel...@googlegroups.com. > >>> To view this discussion on the web visit > https://groups.google.com/d/msgid/haskell-stack/dedd93bb-4488-4b8c-982b-b83776cfdd0e%40googlegroups.com > . > > > > -- > > You received this message because you are subscribed to the Google > Groups "haskell-stack" group. > > To unsubscribe from this group and stop receiving emails from it, send > an email to haskell-stack+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/haskell-stack/09f7bac3-9451-4d62-9ae8-dcf76a3cf150%40googlegroups.com > . > > -- > You received this message because you are subscribed to the Google Groups > "haskell-stack" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to haskell-stack+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/haskell-stack/CAPkELw4%3DyEgsK9qiV2OFMkBv5%2Bfjr7WPnVP9GXk%2BWBFKwu2Mcg%40mail.gmail.com > . > -- You received this message because you are subscribed to the Google Groups "haskell-stack" group. To unsubscribe from this group and stop receiving emails from it, send an email to haskell-stack+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/haskell-stack/CAKA2JgLnyDS_opqU%3DCo9tX1ALdL%2BsemapYFdpaHsaxo6Fp3A_Q%40mail.gmail.com.
