Skip to content

Conversation

@peci1
Copy link
Contributor

@peci1 peci1 commented Apr 27, 2015

<run_depend>vrep</run_depend> should start working as soon as my pull request to rosdistro is accepted and distributed.
It installs V-REP to /opt/vrep .
If it finds an instance of V-REP in this directory, it doesn't do anything to it (not even update).

<run_depend>vrep</run_depend> should start working as soon as my pull request to rosdistro is accepted and distributed.
It installs V-REP to /opt/vrep .
If it finds an instance of V-REP in this directory, it doesn't do anything to it (not even update).
@peci1
Copy link
Contributor Author

peci1 commented Apr 27, 2015

If you accept this and ros/rosdistro#8189 is merged, you may consider adding the vrep dependency in package.xmls of your packages.

@jokla
Copy link
Contributor

jokla commented Apr 27, 2015

Thank you @peci1. When ros/rosdistro#8189 is merged we will consider this useful possibility.

Giovanni

@ricsp
Copy link
Contributor

ricsp commented Oct 21, 2015

I am not sure this is a good idea.
I should rephrase: it is a certainly useful to have the possibility to install vrep automatically, but I am not sure that we can implement this because of licensing considerations.
V-REP is not free for non-academic users and so we cannot automatically download it if the user does not have the right to the free license.
I am not an expert, but I think we should ask coppelia robotics before accepting this PR.
What do you guys think?

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.

3 participants