Read the Generated Package Tree

Before adding code, understand what already exists.

From:

cd ~/ros2_ws/src/robotnix_pubsub

inspect:

ls -la
find . -maxdepth 2 -type f | sort

package.xml

ROS package metadata and dependencies.

setup.py

Python/setuptools installation metadata and console entry points.

setup.cfg

The official tutorial explains that executable scripts are installed under the package's lib location so ros2 run can find them.

resource/robotnix_pubsub

Marker used by the ament resource index.

robotnix_pubsub/__init__.py

Marks the inner directory as a Python package/module location.

test/

Generated Python ROS packages commonly include lint/test files. You do not need to master the testing stack in this beginner course, but do not delete files merely because you do not recognize them.

Checkpoint

For each generated file, answer:

Is this source code, ROS metadata, Python installation metadata, executable-install configuration, or test infrastructure?