You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Better than setting a parameter in the app manager's roslauncher would be an automatic detection of whether or not everything has been set up to support automatic installation of apps.
Our current method is enabling password-less installation using apt-get via sudoers (see #211 for more details).
One method of detecting, if this has been set-up, is actually trying to install a know to be available package (sth standard). However, if in the same shell the user has provided the sudo password before - let's say for the manual installation of a package - the app manager could falsely detect automatic app installation has been enabled.
Need to put some thinking in this to enable a robust detection of this.
The text was updated successfully, but these errors were encountered:
Just launch a command in a python subprocess with a fresh shell, that should work.
Don't even worry about it, just proceed to try every time the user asks to start a rapp, and if it works, great, if it doesn't, pop out a warning of decent immensity and obviality to the user.
is bad. The concert then cannot be sure if such a resource is allocatable before starting it.
So yeah, we have to validate at startup, i.e. detect whether the user can run sudo with apt-get or rosdep or similar.
I don't think we have to go as far as detecting if the user has got temporary sudo access though. It is a minor use case and because it is human interactive, we can always throw them a noisy warning later when an automatic install fails.
Better than setting a parameter in the app manager's roslauncher would be an automatic detection of whether or not everything has been set up to support automatic installation of apps.
Our current method is enabling password-less installation using apt-get via sudoers (see #211 for more details).
One method of detecting, if this has been set-up, is actually trying to install a know to be available package (sth standard). However, if in the same shell the user has provided the sudo password before - let's say for the manual installation of a package - the app manager could falsely detect automatic app installation has been enabled.
Need to put some thinking in this to enable a robust detection of this.
The text was updated successfully, but these errors were encountered: