Superflore, unlike the standard ROS release tool bloom is designed to create release metadata for entire distributions at once rather than individual packages. superflore-gen-ebuilds has an --only flag which suggests that it's possible to restrict the packages which are generated but there is no flag to generate ebuilds for specified packages _and_ their dependencies, which is more than likely what you want.
When reporting problems like this it is best to include both the command that you ran (which you've done) and the output which is most likely related to the error you're requesting assistance with.
I ran superflore-gen-ebuilds --ros-distro rolling --dry-runlocally and confirmed that the issue is packages with conditional build types. I spent some time this afternoon drafting a patch to superflore which implements proper conditional evaluation (https://github.com/ros-infrastructure...). However during the dry run I'm seeing a number of warnings regarding missing system dependencies from rosdep and the run ended with an error running a specific docker image.
Where the packages after the argument --skip-keys would be the ones I ignored so far. I am far from being finished and I saw that these packages are the ones distributed with ros_base but are they essential in order to run ros applications ?
Why are package like lanelet2 in ros base ? Shouldn't it be an external package ?
What gives you the impression that these are packages associated with ros_base? superflore generates ebuilds for the _entire_ ROS distribution.
It looks like there are going to be more issues with superflore's overlay generation than just the above issue. Have you built ROS 2 from source on Gentoo recently? You could follow the ROS 2 development setup (Note: you will need to adapt the documentation to Gentoo as there are not currently gentoo-specific setup instructions.).
Using rosinstall_generator or the ros2.repos file used in the above listed instructions will allow you to test building a smaller set of ROS 2 packages.
depthai_ros_msgsand the other packages you list are definitely not inros_base. See REP-2000 for what is part ofros_basein Galactic.Edit: could you please not cross-post to ROS Discourse?
I guess superflore just compiles every packages listed by rosdistro then. Feels like there should be a way to separate builds between the different packages.
And regarding the post on rosdiscourse. I created it to discuss about the portage of ros to gentoo in general not in order to get answer to this question.