allenh1
commented
2 years ago @alexfanqi Hi!
I see packages in this overlay are generated by automation tool Superflore.
Yes, exactly. To get started, architecture would need to get added here
I'm currently in the midst of getting things back up and running again, and starting to get ros2 going.
Does the main tree merge packages from this overlay? And does the keyword in main tree affect its support in this overlay?
The main tree does not (to my knowledge, at least) merge in the packages from this overlay. The reason this overlay exists is to allow installation of several ROS distributions, have things managed by ROS dependency tools, and install things in the proper locaiton (/opt/ros/[distro]).
Unfortunately, things have kind of fallen apart due to Gentoo's dropping Python 2 (which is more or less a requisite for ROS before the Noetic distribution, see #1015). I've just recently updated much of the core ebuilds, and will be spending time next week to get noetic emerging as much as possible and those changes pushed into superflore.
On another note, is there plan to support RISC-V in this overlay? I would love to help though I only have beginner experience in ROS.
With some help, I'd love to make that happen. I don't have access to a RISC-V system, but am happy to make an effort to support it!
Hi there,
I open this issue to ask about the relation between the in-tree packages and this overlay. I want to clarify this because I am testing ROS for riscv in the main tree and keywording them if possible. I see packages in this overlay are generated by automation tool Superflore. Does the main tree merge packages from this overlay? And does the keyword in main tree affect its support in this overlay?
On another note, is there plan to support RISC-V in this overlay? I would love to help though I only have beginner experience in ROS.
Thanks in advance. Any comments would be really appreciated.