Newest at the top
| 2024-04-26 00:07:18 +0200 | demesne | (~demesne@50.35.88.207) |
| 2024-04-26 00:06:47 +0200 | demesne | (~demesne@50.35.88.207) (Remote host closed the connection) |
| 2024-04-26 00:06:03 +0200 | euleritian | (~euleritia@212.144.241.187) |
| 2024-04-26 00:05:32 +0200 | Achylles | (~Achylles@45.182.57.9) (Read error: Connection reset by peer) |
| 2024-04-26 00:04:27 +0200 | demesne | (~demesne@50.35.88.207) |
| 2024-04-26 00:04:19 +0200 | Achylles | (~Achylles@45.182.57.9) |
| 2024-04-25 23:59:57 +0200 | euleritian | (~euleritia@212.144.241.187) (Ping timeout: 268 seconds) |
| 2024-04-25 23:55:29 +0200 | <cheater> | :) |
| 2024-04-25 23:55:28 +0200 | euleritian | (~euleritia@212.144.241.187) |
| 2024-04-25 23:55:28 +0200 | <cheater> | don't need to figure this one out rn |
| 2024-04-25 23:55:23 +0200 | <cheater> | it's fine though |
| 2024-04-25 23:55:19 +0200 | <cheater> | eh i think the file information should be available somehow somewhere at which point you're just wgeting all things |
| 2024-04-25 23:55:01 +0200 | <cheater> | aye |
| 2024-04-25 23:54:42 +0200 | <haskellbridge> | <sm> poor man's stackage-mirroring workflow, until you find the right way |
| 2024-04-25 23:54:12 +0200 | <haskellbridge> | <sm> actually, copy them from ~/.stack so they all come from the desired snapshot. |
| 2024-04-25 23:54:03 +0200 | <cheater> | that's all i really needed to know |
| 2024-04-25 23:53:59 +0200 | <cheater> | well, i'm satisfied that it's possible |
| 2024-04-25 23:53:35 +0200 | <cheater> | right |
| 2024-04-25 23:53:33 +0200 | <cheater> | like dolio said, that doesn't do much |
| 2024-04-25 23:53:30 +0200 | <haskellbridge> | <sm> sure. But copy them from there to your new dir |
| 2024-04-25 23:53:26 +0200 | <cheater> | so not just download them and use them immediately |
| 2024-04-25 23:53:12 +0200 | <cheater> | well, the idea is to keep those packages around for a while |
| 2024-04-25 23:53:04 +0200 | <cheater> | heh |
| 2024-04-25 23:52:56 +0200 | <haskellbridge> | <sm> if you install a few big packages with either cabal or stack, most of these tarballs will be available under ~/.cabal or ~/.stack :) |
| 2024-04-25 23:50:59 +0200 | <haskellbridge> | <sm> ah |
| 2024-04-25 23:50:35 +0200 | <cheater> | well the idea is for the snapshot to be on my computer |
| 2024-04-25 23:50:20 +0200 | motherfsck | (~motherfsc@user/motherfsck) |
| 2024-04-25 23:50:05 +0200 | <haskellbridge> | <sm> someone here will know how to do that.. discussion here: https://github.com/haskell/cabal/issues/7556 |
| 2024-04-25 23:48:29 +0200 | <haskellbridge> | <sm> do you simply want to point cabal to a stackage snapshot, with a suitable entry in cabal.project ? |
| 2024-04-25 23:47:49 +0200 | <cheater> | the which is the preferable way to use stack |
| 2024-04-25 23:47:32 +0200 | <cheater> | and then you never have to touch stack again |
| 2024-04-25 23:47:22 +0200 | <haskellbridge> | <sm> np. You've still got to get a copy of all needed tarballs |
| 2024-04-25 23:47:21 +0200 | <cheater> | i guess you could use stack with an lts resolver and just hammer all the packages it has one by one and put them in a dir like that |
| 2024-04-25 23:46:44 +0200 | <cheater> | thanks a lot sm |
| 2024-04-25 23:45:48 +0200 | <cheater> | that's exactly how i imagined it |
| 2024-04-25 23:45:43 +0200 | <cheater> | hell yea |
| 2024-04-25 23:45:01 +0200 | <sm> | also: https://cabal.readthedocs.io/en/3.4/installing-packages.html#local-no-index-repositories |
| 2024-04-25 23:44:49 +0200 | yin | (~yin@user/zero) |
| 2024-04-25 23:43:33 +0200 | <cheater> | that's a pretty big assumption you're making there |
| 2024-04-25 23:43:12 +0200 | <dolio> | How does pre-downloading the attack help you avoid that? |
| 2024-04-25 23:42:10 +0200 | <cheater> | you'd think having local copies of package repos would be more popular given the recent rise in supply chain vectors |
| 2024-04-25 23:41:36 +0200 | <sm> | #haskell-stack:matrix.org will know more about how to tackle it with stack |
| 2024-04-25 23:41:36 +0200 | <cheater> | sm yeah that's what this repo refers to at the top of the readme |
| 2024-04-25 23:41:21 +0200 | <geekosaur> | except in the corporate world, and I'm not sure they publish their tools |
| 2024-04-25 23:41:12 +0200 | <sm> | I've seen discussion of "private hackage repositories" somewhere |
| 2024-04-25 23:40:49 +0200 | <cheater> | i guess not a common need |
| 2024-04-25 23:40:47 +0200 | euleritian | (~euleritia@212.144.241.187) (Ping timeout: 264 seconds) |
| 2024-04-25 23:40:42 +0200 | <cheater> | i thought it would be easier |
| 2024-04-25 23:40:35 +0200 | <cheater> | jesus that's pretty complex still though |
| 2024-04-25 23:38:58 +0200 | <cheater> | hmm interesting, ty |