[bad integration policy] When installing, stack extracts a lot of files into /tmp/stack12098

[drake-mer]

Hello, here you go about some thoughts that cross my mind when trying to install stack (it is a snippet of an IRC discussion with me as bbear).

18:12:33] <bbear> http://textuploader.com/5i1pe <-- here you go for the problem.
[18:14:01] <bbear> http://pastie.org/10897904
[18:14:14] <leshow> bbear: yeah?
[18:14:19] <bbear> that's weird, I thought /tmp could handle some data.
[18:14:33] <bbear> leshow, take a look at the above link, it says /tmp is on tmpfs
[18:14:41] <ertesx> bbear: /tmp is usually a RAM-disk
[18:15:02] <bbear> well basically I should try to extract elsewhere ?
[...]
[18:18:08] <bbear> If not, so, what is it doing in /tmp ? You could create a user ~/.tmp20390 folder to do your thing into it.
[18:18:35] <bbear> It would be the same and would avoid, I bet, most problems of sharing files between different file systems.
[18:19:49] <bbear> again if the plan is to move that files (ie copy them elsewhere) the first location to be thought of is not /tmp.

Well, just to say an advice. You should indeed try to create a temp directory into .stack instead of /tmp. /tmp maybe on another file system, or tmpfs (right here in this example it is) and is not made to handle a large volume of data like stack is doing. At the very least, you should add an option to extract packages into the user directory or somewhere else than /tmp.

[nitrix]

Had this issue on a VPS; had to cross-compile and copy the binaries. Unfortunate design decision.

[sjakobi]

This problem is already being tracked in #996. I believe your ideas were already discussed there but please chime in if that issue is still missing some aspects.