5.2 Ports with distribution restrictions

5.2.1 NO_PACKAGE

This variable indicates that we may not generate a binary package of the application. However, the port's DISTFILES files may be freely distributed.

NO_PACKAGE should also be used if the binary package is not generally useful, and the application should always be compiled from the source code. For example, if the application has configuration information that is site specific hard coded in to it at compile time.

NO_PACKAGE should be set to a string describing the reason why the package should not be generated.

5.2.2 NO_CDROM

This variable indicates that although we are allowed to generate binary packages, we are not allowed to put those packages, or the port's DISTFILES, on to CDROM for resale. The DISTFILES will still be available via FTP.

NO_PACKAGE and NO_CDROM can be set simultaneously.

5.2.3 RESTRICTED

Set this variable if the application's license also forbids us from mirroring the application's DISTFILES via FTP.

Also set this if the application's license has general restrictions on who may use it. Examples include:

• The application is for non-commercial use only.

• The application contains cryptography code which is forbidden in some countries.

5.2.4 RESTRICTED_FILES

If only some of the distribution files are restricted then set this variable to list them. It defaults to ${DISTFILES} ${PATCHFILES}.