Community
Participate
Working Groups
Currently, Remote Tools executes remote commands using /bin/sh. This assumes /bin/sh is the correct path, which is not guaranteed. Also, the API doesn't provide a way to query the type of the shell (bash, dash, etc.). To be more robust, Remote Tools could search for a suitable shell, in case /bin/sh is not suitable, and should have an API to query what type the shell is (bash, dash, etc.). For this to be feasible, there can be a minimum requirement for systems as to what shells are supported and where they are located. Benefits of this feature include: 1) Limited list of shells to be tested 2) Allow different code for different shells where needed.
The org.eclipse.remote component of the Eclipse Ecosystem has a new home. It is now part of the Eclipse CDT project[1]. This change means a new Git repo[2], P2 site[3] and Bugzilla component. The org.eclipse.remote will continue to be delivered as part of the quarterly Simultaneous Release of Eclipse as well. If this bug is no longer relevant, please feel free to comment or close the bug. If you can confirm if this issues still occurs in the latest release please do let me know in a comment. [1] https://wiki.eclipse.org/CDT/User/NewIn106 [2] https://git.eclipse.org/c/cdt/org.eclipse.cdt.git (in the remote directory) [3] first CDT release will be 10.6 - P2 site will be https://download.eclipse.org/tools/cdt/releases/10.6/ (This comment was added to all relevant org.eclipse.remote bugs along with changing the Product/component pair to CDT/remote.)
