Hi, I was excited to read the blog post about this new feature but was disappointed that exactly my main use case for it was explicitly blocked.
I get the argument about snapshots being supposed to be immutable. However, I need to ship the code and dependencies over to the customers side for compliation without internet access. Right now my approach is to `stack build --prefetch --dry-run` and tar up the resulting STACK_ROOT. On customer side I can create a STACK_ROOT and compile without connection. Unfortunately, the tarball is bigger than I'd like. I hoped to build an immutable - yet local path based - custom snapshot that is about the size the dependencies I really have. Given this use case, would you reconsider if local paths could be allowed? I imagine this is technically easy, you just don't advise having mutable snapshots. I would happily take the responsibility for making sure my snapshots are immutable. I hope my use case is clearly stated and gets at least some consideration. If you have any further questions or advice how to achieve the same without local paths in custom snapshots that would be appreciated as well. Best regards Jan -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/haskell-stack/16b16642-2997-466a-b7ef-cfe509260bae%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
