Skip to content
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

Resolve package paths and repos #1

Closed
fmauch opened this issue Jul 31, 2020 · 3 comments
Closed

Resolve package paths and repos #1

fmauch opened this issue Jul 31, 2020 · 3 comments
Assignees

Comments

@fmauch
Copy link
Contributor

fmauch commented Jul 31, 2020

As raised earlier (e.g. here there currently are problems with getting the correct subdir for individual packages.

Now, without having looked at the code too deeply, I think that the following should work:

  • Take the URL from the rosdistro's distribution.yaml
  • append archive/release/melodic/<pkg_name>/<version>.tar.gz
  • Set the directory to the first (and only) subdirectory inside the extracted archive

The names don't seem to be consistent, as for example, for ros_control_boilerplate it is ros_control-release-release-melodic-combined_robot_hw while for moveit_ros_benchmarks it is moveit-release-release-melodic-moveit_ros_benchmarks-1.0.5-1.

I just wanted to raise this issue here to start discussing it.

@fmauch
Copy link
Contributor Author

fmauch commented Jul 31, 2020

If we swap this if/else

and use this URL directly to generate the versioned URL instead of extracting the target first, this should be working. What do you think @bionade24?

@bionade24 bionade24 self-assigned this Jul 31, 2020
@bionade24
Copy link
Collaborator

If we swap this if/else
You mean the if/elif, don't you?
and use this URL directly to generate the versioned URL instead of extracting the target first, this should be working. What do you think @bionade24?
I'm can't follow your idea. Why should be the 1st folder in the tarball be correct?
What has the release tarball URL generation to do with the tarball itself?
A bit of (at least pseudo) code would probably make your idea more clear. Thx for spending your time on this project.

@fmauch
Copy link
Contributor Author

fmauch commented Jul 31, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants