Page MenuHomeFreeBSD

Introduce UNKNOWN license
ClosedPublic

Authored by AMDmi3 on Sep 7 2016, 5:44 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, Feb 7, 4:36 PM
Unknown Object (File)
Dec 22 2025, 12:23 AM
Unknown Object (File)
Nov 24 2025, 7:50 AM
Unknown Object (File)
Nov 24 2025, 5:53 AM
Unknown Object (File)
Nov 21 2025, 5:35 PM
Unknown Object (File)
Nov 19 2025, 4:42 PM
Unknown Object (File)
Nov 18 2025, 8:44 AM
Unknown Object (File)
Nov 18 2025, 5:22 AM
Subscribers

Details

Summary

Some ports do not define license. These may be unsafe to use from legal point of view, so we need to state that in the port's Makefiles. Also we need to distinguish ports with unspecified license from ports which have not yet set LICENSE.

So introduce UNKNOWN license.

Topics for dicussion:

  • Name: UNSPECIFIED/NONE/UNKNOWN/lowercase equivalents?
  • Default permissions: auto-accept to preserve current bahavior and not bug users with a need to confirm the license or no-auto-accept to be on a safe side?

We may instead consider a special handling for these cases, e.g. using NO_LICENSE knob instead, with separate warnings and a way to allow/disallow ports marked as such. This would be non-generic are require more code though.

Test Plan

This license is used for net/p5-Net-Ping, which has unknown license (as explicitly stated in META.json and META.yml)

Diff Detail

Repository
rP FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

AMDmi3 retitled this revision from to Introduce UNKNOWN license.
AMDmi3 updated this object.
AMDmi3 edited the test plan for this revision. (Show Details)
AMDmi3 edited edge metadata.

As suggested by bapt@ and to avoid confusion, rename to NONE (e.g. no license specified)

bapt added a reviewer: bapt.
This revision is now accepted and ready to land.Sep 8 2016, 11:57 AM