Release as installable package

[K-Zanaty]

There should be no source code to share, an installable package should be created using the GitHub pipelines.

[MilesOuirari]

i think it should be created by snapcraft : https://docs.ros.org/en/foxy/Tutorials/Miscellaneous/Packaging-your-ROS-2-application-as-a-snap.html

[K-Zanaty]

@MilesOuirari mentioned, remaining effort: 2-3 days

[K-Zanaty]

@MilesOuirari There is no branch created for this, last status update from 26.3.

[K-Zanaty]

@MilesOuirari Please keep in mind, that ideally, packages are created in a pipeline with the latest version number upon GitHub release. Thus, the developer does not need to think about building by themselves and push some packages

[MilesOuirari]

in resume : first approach is using bloom : for bloom i was able to generate a debian image , but when testing there was some disfonctionality , bloom dont use ament_python to build a package but instead it use ament_cmake_python . okay and if we use ament_cmake_python and Build error when using ament_python_install_package() and generated interfaces #141 this is known issue from ros 2 , https://github.com/ros2/rosidl_python/issues/141 , to bypass this two solution is possible :

• develop everything with c++ and build only with cmake (this take 3 days with testing)
• build two package , having two image one for ros2 interfaces definition like actions and service the other for python script package , then deliver two binary deb file and launching together with a bash script (this method is hypothetical and perhaps lead to a solution)

second approach is to deliver a docker image . (for this approach i need to use a native ubuntu laptop since the wsl2 on windows run on docker and some issue appear when i try to launch it ) (on native linux this solution takes 2 days with testing )

[K-Zanaty]

@MilesOuirari Further investigation postponed until end of May 2024 (delivery of customer project SP Automation&Robotics)

Developing with C++?