Page MenuHomeFreeBSD

Set licenses for the PyQt ports
ClosedPublic

Authored by tcberner on Nov 12 2017, 9:13 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Mar 14, 2:27 AM
Unknown Object (File)
Wed, Feb 28, 8:05 AM
Unknown Object (File)
Feb 25 2024, 3:59 PM
Unknown Object (File)
Feb 18 2024, 8:12 AM
Unknown Object (File)
Jan 27 2024, 11:17 AM
Unknown Object (File)
Jan 27 2024, 11:17 AM
Unknown Object (File)
Jan 27 2024, 11:16 AM
Unknown Object (File)
Jan 27 2024, 11:03 AM
Subscribers

Details

Reviewers
jrm
adridg
Group Reviewers
kde
O5: Ports Framework(Owns No Changed Paths)
portmgr
Commits
rP457606: Define licence for PyQt ports via pyqt.mk
Summary
  • both are GPLv3 at the moment

Diff Detail

Repository
rP FreeBSD ports repository
Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 12680
Build 12951: arc lint + arc unit

Event Timeline

Mk/Uses/pyqt.mk
208

^ note I intentionally made this overridable

In D13055#271762, @jrm wrote:

Looks good to me.

Are there implications here for pyqt being dual licensed?
PyQt is dual licensed on all supported platforms under the GNU GPL v3 and the Riverbank Commercial License

Means I should probably modify that slightly :)

adridg added a subscriber: adridg.

While it is true that the license on PyQt is dual GPLv3 and Riverbank's license (RCL), the artifacts produced by the ports build system do not meet the requirements of the RCL (since they're tied to a single application, preferably statically linked). So even if you have an RCL, you can't use this -- so just stick to GPLv3.

This revision was not accepted when it landed; it landed in state Needs Review.Dec 30 2017, 6:01 PM
This revision was automatically updated to reflect the committed changes.