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

depend on curl (libcurl-dev, curl) for packaging #25

Merged
merged 1 commit into from
Jun 15, 2018

Conversation

mikaelarguedas
Copy link
Member

Defining the dependency on curl allows us to not build it from source but just depend on the upstream version.
Copied from: https://github.com/ros2-gbp/resource_retriever-release/tree/5597bf018cfe1bcf3e323c50801bb89c946e9061/ubuntu/libcurl_vendor

The key resolves to libcurl-dev and curl:
https://github.com/ros/rosdistro/blob/f236f31615f7eb1667e94cba66f212ddcb80829b/rosdep/base.yaml#L524

@nuclearsandwich @wjwwood @clalancette FYI

@mikaelarguedas
Copy link
Member Author

I'm holding this for now as the new rosdep rule pointing to the virtual package libcurl-dev seems to cause issues on the farm: ros/rosdistro#15308 (comment)

@nuclearsandwich
Copy link
Member

Since that issue affects us whether we have the dependency here or patched in via the release repository we need to figure it out. The potential solutions I can see in order of most effective to most expedient are

  • Add support for virtual packages described in Depend on generic libcurl-dev rosdistro#15308 (comment)
  • Revert the PR using the libcurl-dev virtual package
  • Patch the debian/control file for this package in ROS 2 to use the concrete package instead of the virtual one.
  • Use a locally modified rosdep database when blooming to resolve the key to the concrete package.

@mikaelarguedas
Copy link
Member Author

ros/rosdistro#15308 has been reverted.

This key now points to libcurl4-openssl-dev, curl.

Merging this patch

@mikaelarguedas mikaelarguedas merged commit 0f10e6b into ros2 Jun 15, 2018
@mikaelarguedas mikaelarguedas deleted the ros2_depend_on_curl branch June 15, 2018 13:25
nuclearsandwich pushed a commit to ros/rosdistro that referenced this pull request Apr 19, 2019
…20969)

Increasing version of package(s) in repository `resource_retriever` to `2.1.0-1`:

- upstream repository: https://github.com/ros/resource_retriever.git
- release repository: https://github.com/ros2-gbp/resource_retriever-release.git
- distro file: `dashing/distribution.yaml`
- bloom version: `0.8.0`
- previous version for package: `null`

## libcurl_vendor

```
* depend on curl (mapping to curl, libcurl4-openssl-dev) for packaging (#25 <ros/resource_retriever#25>)
* add missing dependency on pkg-config (#19 <ros/resource_retriever#19>)
* [libcurl_vendor] convert to ament and setup env hooks for library paths (#14 <ros/resource_retriever#14>)
* Contributors: Dirk Thomas, Mikael Arguedas, William Woodall
```

## resource_retriever

```
* Make sure to export the include directory for resource_retriever. (#22 <ros/resource_retriever#22>)
* Contributors: Chris Lalancette
```
andre-rosa pushed a commit to andre-rosa/rosdistro that referenced this pull request May 3, 2019
…os#20969)

Increasing version of package(s) in repository `resource_retriever` to `2.1.0-1`:

- upstream repository: https://github.com/ros/resource_retriever.git
- release repository: https://github.com/ros2-gbp/resource_retriever-release.git
- distro file: `dashing/distribution.yaml`
- bloom version: `0.8.0`
- previous version for package: `null`

## libcurl_vendor

```
* depend on curl (mapping to curl, libcurl4-openssl-dev) for packaging (ros#25 <ros/resource_retriever#25>)
* add missing dependency on pkg-config (ros#19 <ros/resource_retriever#19>)
* [libcurl_vendor] convert to ament and setup env hooks for library paths (ros#14 <ros/resource_retriever#14>)
* Contributors: Dirk Thomas, Mikael Arguedas, William Woodall
```

## resource_retriever

```
* Make sure to export the include directory for resource_retriever. (ros#22 <ros/resource_retriever#22>)
* Contributors: Chris Lalancette
```
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

Successfully merging this pull request may close these issues.

None yet

2 participants