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
I propose that we work towards making new releases of our project into .deb packages that can be easily installed on target machines with sudo apt-get install ros-melodic-ez-rassor
The ROS community created a tool, bloom, to package catkin packages such as ours into the ROS buildFarm. From there, this process would automatically make a .deb package available for use through the normal ROS ppa's.
Modifying our installation script
I propose that we significantly scale back the operations of our install script. This includes:
Using a visible workspace to house our code instead of a hidden workspace
Removing the reliance on our custom script to perform build and install operations (operations should be done through the built in ROS commands)
Why I feel this is needed
Our repository currently caters to 2 types of people: Developers & End Users. Even though we have documentation to back up everything we do, ROS developers are discouraged from using the experience they already have (i.e., navigating to a public workspace and making changes vs using our script which abstracts that away) and end users are forced to go through multiple commands to get our project installed.
I realize that the second use case (end user) isn't that big of an issue since our install script works in a one-liner fashion. But they would still need to download our repository to run our software which would be unnecessary if we are able to install the project through apt-get as is the norm.
Ultimately, I believe the EZ-RASSOR project would be better for both groups if we package our software. This would also help us containerize our app and even get it running on other platforms easily through tools like WSL.
The text was updated successfully, but these errors were encountered:
Adding bloom functionality
I propose that we work towards making new releases of our project into .deb packages that can be easily installed on target machines with
sudo apt-get install ros-melodic-ez-rassor
The ROS community created a tool, bloom, to package catkin packages such as ours into the ROS buildFarm. From there, this process would automatically make a .deb package available for use through the normal ROS ppa's.
Modifying our installation script
I propose that we significantly scale back the operations of our install script. This includes:
Why I feel this is needed
Our repository currently caters to 2 types of people: Developers & End Users. Even though we have documentation to back up everything we do, ROS developers are discouraged from using the experience they already have (i.e., navigating to a public workspace and making changes vs using our script which abstracts that away) and end users are forced to go through multiple commands to get our project installed.
I realize that the second use case (end user) isn't that big of an issue since our install script works in a one-liner fashion. But they would still need to download our repository to run our software which would be unnecessary if we are able to install the project through apt-get as is the norm.
Ultimately, I believe the EZ-RASSOR project would be better for both groups if we package our software. This would also help us containerize our app and even get it running on other platforms easily through tools like WSL.
The text was updated successfully, but these errors were encountered: