Remote depends on GNU/Bash

[juergenhoetzel]

Part of local issues are fixed in 3862ab7, but if
remote target is a FreeBSD-System:

freebsd@rpi2:22 | export: Command not found.
freebsd@rpi2:22 | export: Command not found.

[VojtechVitek]

@juergenhoetzel is your default shell TCSH?

[juergenhoetzel]

@VojtechVitek yes, TCSH is the default Shell on FreeBSD

IMHO the best solution would be to just rely on POSIX features

[pkieltyka]

agreed on replying only on POSIX commands

[VojtechVitek]

hmm........ this is tricky, since export VAR=val actually exports the var to all child processes

I guess I could use set or setenv instead but there might be hidden edge cases.

[juergenhoetzel]

agreed on replying only on POSIX commands

Actually export=is valid POSIX.
Invoking /bin/shexplicitly could be used to enforce evaluation using a POSIX shell, whether or not the users account is set to a POSIX shell

[VojtechVitek]

@juergenhoetzel can you verify that your FreeBSD system doesn't have TCSH on /bin/sh path?

[juergenhoetzel]

@juergenhoetzel can you verify that your FreeBSD system doesn't have TCSH on /bin/sh path?

I can confirm. /bin/sh is always the default POSIX sh: https://www.freebsd.org/cgi/man.cgi?query=sh&sektion=&n=1

[pkieltyka]

yea.. you can definitely expect any POSIX OS to have /bin/sh

[VojtechVitek]

Might be solved by #77.