On 06/09/08, Mike Sullivan wrote: > > though I'd wonder what it is doing in HOME before I chose what to > set it to. If it just needs it set to something, it doesn't matter. > But if it's going to be scribbling around in $HOME/.somefilename then > you shouldn't set HOME to something common like /tmp or multiple builds > on the same machine might fail interestingly if they collide in erlang. > In that case I'd probably set it to something in your build area > (like if you're building erlang, $SRC/cmd/erlang/tmp or whatever) and > I might even do it in each Makefile.sfw instead so that it's the > same for each person who builds it and it doesn't leave things in > folks home directories. >
In this case, I guess it only checks if there are some special files under HOME dir(I asked this on Erlang mailing list, but unfortunately didn't get helpful answer). But I think you suggestion is right. I will set HOME to build-specific directory to avoid any potential conflicts between parallel builds. The reason why I asked this is that I thought it would be better if HOME could be set in env files used by nightly, rather than in each application subdir. Thanks, Raymond
