ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange
Ask Your Question

Releasing ROS packages under LGPL/BSD

asked 2012-08-08 08:05:21 -0600

I am writing a ROS wrapper for a library released under LGPL. I had a few questions regarding releasing the ROS Wrapper:

  1. The library gets downloaded as a ROS Package. I assume that this package should be marked as LGPL?
  2. Since no modifications were made to the library, the ROS Wrapper (inside the same stack) can be licensed under BSD?
  3. The overarching stack with 3-4 packages can still be released under the BSD?
  4. Given the ROS paradigm, if a stack does not need to be modified locally by the end user, does it matter if it is released under a BSD or LGPL license?

Similar questions seem to have been discussed for GPL vs BSD in this thread:

edit retag flag offensive close merge delete

1 Answer

Sort by » oldest newest most voted

answered 2012-08-08 10:01:47 -0600

Eric Perko gravatar image

I'll comment with my understanding..

  1. Yes, that package should be LGPL, because it is distributing the LGPL component (and if you went and looked at the source code, it would be LGPL licensed).
  2. Yes, your ROS wrapper that simply links against the LGPL code can be BSD, as long as it doesn't include any LGPL code (e.g. you didn't copy-paste anything from the LGPL code into your BSD code)
  3. The overaching stack should list it's license as BSD/LGPL because it does contain some LGPL code in that library wrapper package.
  4. BSD makes it easier if the user does need to modify it. Remember you aren't so much licensing the entire stack as just listing the licenses used by each of the packages in it. And even then, the actual license is whatever is in each file/library (e.g. the standard BSD header at the top of most of the core ROS files).
edit flag offensive delete link more

Question Tools


Asked: 2012-08-08 08:05:21 -0600

Seen: 563 times

Last updated: Aug 08 '12