Revision history [back]

Would using ROSDISTRO_INDEX_URL perhaps be an option?

I cannot really find any 'official' documentation for it, but from what I've understood from this answer from William on the buildbot-ros-sig, and from @tfoote in Bloom - "Could not resolve rosdep key 'message_runtime'" on ROS Answers, you should be able to just create a copy of the rosdistro files that normally go into /etc/ros anywhere your user does have write permission, and then update ROSDISTRO_INDEX_URL to point to that location.

I have no idea whether that environment variable is used throughout all bits that deal with dependency resolution, but it might be worth a shot.

Would using ROSDISTRO_INDEX_URL perhaps be an option?

I cannot really find any 'official' documentation for it, but from what I've understood from this answer from William on the buildbot-ros-sig, and from @tfoote in Bloom - "Could not resolve rosdep key 'message_runtime'" on ROS Answers, you should be able to just create a copy of the rosdistro files that normally go into /etc/ros anywhere your user does have write permission, and then update ROSDISTRO_INDEX_URL to point to that location.

I have no idea whether that environment variable is used throughout all bits that deal with dependency resolution, but it might be worth a shot.

Would using ROSDISTRO_INDEX_URL perhaps be an option?

I cannot really find any 'official' documentation for it, but from what I've understood from this answer from William @William on the buildbot-ros-sig, and from @tfoote in Bloom - "Could not resolve rosdep key 'message_runtime'" on ROS Answers, you should be able to just create a copy of the rosdistro files that normally go into /etc/ros anywhere your user does have write permission, and then update ROSDISTRO_INDEX_URL to point to that location.

I have no idea whether that environment variable is used throughout all bits that deal with dependency resolution, but it might be worth a shot.

Edit: the xylem design doc also mentions ROSDISTRO_INDEX_URL:

[..]

• Do the API calls respect the XYLEM_PREFIX environment variable or need explicit setting of a prefix parameter? I think the latter.
  • Dirk: For rosdistro we actually do the first approach - the environment variable ROSDISTRO_INDEX_URL is also used for API calls (if not overridden by passing a custom index url). I think that approach has the advantage that any tool using rosdistro will use the custom url when it is defined in the environment.

[..]

Would using ROSDISTRO_INDEX_URL perhaps be an option?

I cannot really find any 'official' documentation for it, but from what I've understood from (from this answer from @William on the buildbot-ros-sig, and from @tfoote in Bloom - "Could not resolve rosdep key 'message_runtime'" on ROS Answers, Answers) you should be able to just create a copy of the rosdistro files that normally go into /etc/ros anywhere your user does have write permission, and then update ROSDISTRO_INDEX_URL to point to that location.

I have no idea whether that environment variable is used throughout all bits that deal with dependency resolution, but it might be worth a shot.

Edit: the xylem design doc also mentions ROSDISTRO_INDEX_URL:

[..]

• Do the API calls respect the XYLEM_PREFIX environment variable or need explicit setting of a prefix parameter? I think the latter.
  • Dirk: For rosdistro we actually do the first approach - the environment variable ROSDISTRO_INDEX_URL is also used for API calls (if not overridden by passing a custom index url). I think that approach has the advantage that any tool using rosdistro will use the custom url when it is defined in the environment.

[..]