Dann Martens

I ran a test on an Ubuntu 20.04 VM, where I intercepted cp calls from rebar3, in order to add "/." to the source path and that seems to fix...

It would appear that the code in this cp_r function will always malfunction with directories on Linux, as it ensures that the directory exists before performing the copy. In that...

Well, I am puzzled as to how this could be something isolated to my setup. It's a very simple project, without any directory-related configuration. This is what "rebar3 compile" sends...

The code only has an exception for OSX as "darwin." It is clear what rebar3 calls for, and that is not the correct command to copy the contents of a...

While I agree that any exoticism of an underlying file system can introduce weird behaviour, I see nothing irregular here. The copy command rebar3 constructs simply _cannot_ work on a...

No, it's not a link. It's a directory open to any and all. There is definitely a clue in that `cp` gets called, if, as you say, it would have...

I just checked that and that fails: ``` ln: failed to create symbolic link 'test/priv': Operation not supported ``` I guess that's why the `cp` is attempted afterwards. Let me...

Yes, the underlying host os only allows symlinks on its file system when the guest runs with elevated privileges, which is not the case. I will send a pull request...

Not an issue, I will look into it and will try to find the best solution to amend this. Pull request coming for you to evaluate.

So far, I've managed to make all the tests pass, except one, which crashes completely: ``` %%% rebar_escriptize_SUITE: ... %%% rebar_escriptize_SUITE ==> escriptize_with_ebin_subdir: FAILED %%% rebar_escriptize_SUITE ==> {thrown,rebar_abort} ``` Since...