Highly Reusable Software

By activity
Professions, Sciences, Humanities, Business, ...

User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...

Text Strings
Conversions, tests, processing, manipulation,...

Math
Integer, Floating point, Matrix, Statistics, Boolean, ...

Processing
Algorithms, Memory, Process control, Debugging, ...

Stored Data
Data storage, Integrity, Encryption, Compression, ...

Communications
Networks, protocols, Interprocess, Remote, Client Server, ...

Hard World
Timing, Calendar and Clock, Audio, Video, Printer, Controls...

File System
Management, Filtering, File & Directory access, Viewers, ...

Reporting when incompatible licenses are used

Read How LIDESC detects and reports licensing conflicts for an overview and web-based demonstration. This page describes how to use the command line utility to report licensing conflicts.

CAUTION: license compatibility reports are only as good as the description files created by human interpretation of license texts. You should obtain them from trusted suppliers, and be careful when creating them yourself. If a symbol list for a license is empty or incomplete, it is not possible to accurately report incompatibility.

WARNING: It is folly to assume that a simple program like this can do anything more than find and report some of the biggest problems, while leaving others undetected. This system does not match the educated human intelligence required to interpret and apply licenses. On the other hand, it can be useful to identify some of the license clauses which deserve extra scrutiny.

The command line to check for licensing conflicts is:

	lidesc [-d {license-dir}] combine license.txt license2.txt . . .

More than two licenses can be given on the command line.

Example output: (following the instructions in Reporting if a license is GPL compatible)

CONFLICT: License bsdorig.txt with TAG librock_LIDESC_COMBINE_GPL_FAIL cannot be combined with gpl.txt
CONFLICT: License bsdorig.txt with TAG librock_ADVNOTE_1C_MENTF cannot be combined with gpl.txt

LIDESC allows creating description files for the purpose of compatibility testing. To see examples of this use:
Reporting if a license is free software according to the FSF
Reporting if a license is closed-source compatible
Reporting if a license is open source software according to the Open Source Definition

Up to: LIDESC User Documentation

Librock LIDESC. Software License Analyzer and Compatibility Reporter
Copyright 2001-2002, Forrest J. Cavalier III, Mib Software
You may reproduce verbatim copies of this page, but changing it is not allowed.
Email: Contact