4 ms·

That's not correct. At its level systemd is just a component, it's not linked against anything that would cause it to be incompatible and all communication wit

That's not correct. At its level systemd is just a component, it's not linked against anything that would cause it to be incompatible and all communication with systemd and its parts are through process-level interfaces (like D-Bus and signals). OpenSolaris, and certainly its derivatives, ship with many GPL and LGPL'd components as far as I'm aware. At this level it falls under GPL's "mere aggregation" clause.

synchronise 13y ago
It would still form part of a greater work and have to be shipped under the GPL, which is incompatible with the CDDL, so in the end you really can't do it.
- kmacleod 13y ago
  The OpenIndiana package repository[1] appears to contain several dozen (counting all Gnome packages as just one) GPL'd packages as part of the OpenIndiana-distributed greater work. Can you be more specific as to why this one package would be different? [1] http://pkg.openindiana.org/dev/en/catalog.shtml http://pkg.openindiana.org/dev/en/catalog.shtml
  - synchronise 13y ago
    Requirement to statically link against CDDL elements, which is still not permitted by the LGPL.
    - kmacleod 13y ago
      LGPL allows for static linking. The distributor need only be able provide the binary library elements necessary to re-link the LGPL library against. OpenIndiana already provides those. In other contexts, it wouldn't even matter if they were wholly closed-source binary libraries as long as they can be re-linked against. (Aside as an example, in our case of an embedded system, our lawyer has cleared us to do exactly this: link a LGPL'd source file against our proprietary application as long as we provide the ability to re-compile and re-link the LGPL'd source file against our code, delivered as a library.) Also, the GPL'd portions linking against the CDDL system libraries (as all the other GPL'd packages do) fall under the system library exception.

synchronise 13y ago

It would still form part of a greater work and have to be shipped under the GPL, which is incompatible with the CDDL, so in the end you really can't do it.

kmacleod 13y ago
The OpenIndiana package repository[1] appears to contain several dozen (counting all Gnome packages as just one) GPL'd packages as part of the OpenIndiana-distributed greater work. Can you be more specific as to why this one package would be different? [1] http://pkg.openindiana.org/dev/en/catalog.shtml http://pkg.openindiana.org/dev/en/catalog.shtml
- synchronise 13y ago
  Requirement to statically link against CDDL elements, which is still not permitted by the LGPL.
  - kmacleod 13y ago
    LGPL allows for static linking. The distributor need only be able provide the binary library elements necessary to re-link the LGPL library against. OpenIndiana already provides those. In other contexts, it wouldn't even matter if they were wholly closed-source binary libraries as long as they can be re-linked against. (Aside as an example, in our case of an embedded system, our lawyer has cleared us to do exactly this: link a LGPL'd source file against our proprietary application as long as we provide the ability to re-compile and re-link the LGPL'd source file against our code, delivered as a library.) Also, the GPL'd portions linking against the CDDL system libraries (as all the other GPL'd packages do) fall under the system library exception.