Nodes from pure python packages can't be started via ros2 run on Linux #41
Description
Running the command ros2 run demo_nodes_py demo_talker results in an error:
(rosurdfdom) traversaro@IITICUBLAP257:~$ ros2 run demo_nodes_py demo_talker
No executable found
While the same command on Windows works fine:
(ros-humble) C:\Users\STraversaro>ros2 run demo_nodes_py demo_talker
[INFO] [1674722953.116532500] [talker]: Publishing: "Hello World: 0"
[INFO] [1674722953.946947500] [talker]: Publishing: "Hello World: 1"
[INFO] [1674722954.944548600] [talker]: Publishing: "Hello World: 2"
The problem is that the executables/entry points on Linux are installed in <install_prefix>/bin, instead of the correct location <install_prefix>/lib/<pkg_name>.
This is kind of a regression of RoboStack/ros-galactic#74, as there the problem affected Windows packages, now Linux (and I guess macOS) packages.