Skip to content
This repository was archived by the owner on Oct 23, 2025. It is now read-only.

Update REP-142 with some fixes found during REP-150 review.#165

Merged
clalancette merged 1 commit intomasterfrom
rep142-update
Mar 19, 2018
Merged

Update REP-142 with some fixes found during REP-150 review.#165
clalancette merged 1 commit intomasterfrom
rep142-update

Conversation

@clalancette
Copy link
Copy Markdown
Contributor

In particular:

  1. Remove "extends" from "ros_core" definition, since extends
    is meant to be used for other meta-packages.
  2. Add "ros" and "ros_comm" into "ros_core" package list.
  3. Remove "console_bridge" from "ros_core" packages, since
    it is provided by the system since Trusty (Indigo).
  4. Move "angles" from "ros_base" to "desktop", since it is
    a dependency of common_tutorials.
  5. Make viz extend from "ros_base" instead of "robot".

Signed-off-by: Chris Lalancette clalancette@openrobotics.org

In particular:

1.  Remove "extends" from "ros_core" definition, since extends
    is meant to be used for other meta-packages.
2.  Add "ros" and "ros_comm" into "ros_core" package list.
3.  Remove "console_bridge" from "ros_core" packages, since
    it is provided by the system since Trusty (Indigo).
4.  Move "angles" from "ros_base" to "desktop", since it is
    a dependency of common_tutorials.
5.  Make viz extend from "ros_base" instead of "robot".

Signed-off-by: Chris Lalancette <clalancette@openrobotics.org>
@clalancette clalancette merged commit f77dd0b into master Mar 19, 2018
@clalancette clalancette deleted the rep142-update branch March 19, 2018 14:16
@mikaelarguedas
Copy link
Copy Markdown
Contributor

@dirk-thomas how should we proceed on the metapackages side? update the indigo-devel and kinetic-devel branches accordingly but not the jade-devel as Jade is EOL?

@dirk-thomas
Copy link
Copy Markdown
Member

I would ask @clalancette to create follow up PRs against all branches. And after they have been merged we only release into non-EOL distros.

@clalancette
Copy link
Copy Markdown
Contributor Author

I would ask @clalancette to create follow up PRs against all branches. And after they have been merged we only release into non-EOL distros.

Doing that now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants