"Sergei Golovan" <[EMAIL PROTECTED]> writes: > Erlang compiler reads $HOME/.erlang if it exists. It's contents may > have impact on the package. If the compiler cannot read $HOME it > reports an ugly error message (though it still works). But an > additional tool which is used in wings3d crashes if it cannot read > $HOME. So, setting HOME to something like $(CURDIR)/debian makes > package buildable and consistent (it doesn't depend on $HOME/.erlang > anymore).
> So, I think that at least for erlang-based packages it's better to > redefine HOME environment varibles. Is there a better solution? Doesn't the Erlang compiler support a command-line flag that suppresses that behavior? And if not, wouldn't that be useful to add? -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
