-
Notifications
You must be signed in to change notification settings - Fork 171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial OpenEmbedded support for rosdep #673
Initial OpenEmbedded support for rosdep #673
Conversation
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <recipe>@<meta-layer>, where <recipe> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
Looks like the CI failure relates to the required dependencies. Please advise on the best way to proceed. |
* Is required by related changes in rosdep, rosdistro ros-infrastructure/rosdep#673 ros/rosdistro#20763 * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
8c903a8
to
7534e19
Compare
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <recipe>@<meta-layer>, where <recipe> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
7534e19
to
1339d8b
Compare
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
1339d8b
to
6bf9b03
Compare
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Is required by related changes in rosdep, rosdistro ros-infrastructure/rosdep#673 ros/rosdistro#20763 * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
This needs an updated version dependency on that |
6bf9b03
to
b4c9884
Compare
Thank you, @dirk-thomas ! I updated rospkg >= 1.1.8 dependency. |
b4c9884
to
24c3859
Compare
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
This is failing CI due to the yaml_load deprecation. It's fixed in a follow up commit on this PR: c7a76ef I think that's reasonable to land soon and then this will work. |
24c3859
to
54c8d70
Compare
Codecov Report
@@ Coverage Diff @@
## master #673 +/- ##
=========================================
Coverage ? 75.86%
=========================================
Files ? 32
Lines ? 3016
Branches ? 0
=========================================
Hits ? 2288
Misses ? 728
Partials ? 0
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall it looks fine. However for future users and developers some pointers to the fact that these functions are not fully impelemented will be important to help people understand what's happening as well as let people know what needs to be implemented to reach full expected functionality.
It would probably be worth putting a comment in the doc block too about these being stubs at the moment, not full implementations.
* Requires related changes in rospkg 1.1.8 and rosdistro ros/rosdistro#20763 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
54c8d70
to
d66183d
Compare
Agree, thanks. I added raising NotImplementedError and left comments for the unimplemented stubs. |
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
@tfoote Is this one ready to be merged? |
Yes, it's waiting for @wjwwood who's top priority is the Dashing API freeze this week. |
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
* Requires related changes in rospkg, rosdep ros-infrastructure/rospkg#166 ros-infrastructure/rosdep#673 * Let us map the generic system dependency name into a recipe name available from OE layer index at http://layers.openembedded.org * Mapping is based on PACKAGE_ARGUMENT free form format of <package>@<meta-layer>, where <package> resides in the OE <meta-layer> * Please see the proposal below: https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401
Initial OpenEmbedded support for rospkg rospkg#166
Initial OpenEmbedded support for rosdistro ros/rosdistro#20763
available from OE layer index at http://layers.openembedded.org
package @ meta-layer , where package resides in the OE meta-layer
https://discourse.ros.org/t/a-proposal-for-a-superflore-oe-recipe-generation-scheme/8401