Or QML, in fact:
// Attribution.qml in QtAttribution module:
QtObject {
property string name
property list<string> files
property list<string> upstreamFiles
// ....
}
// Actual attribution.qml in source tree:
import QtAttribution
Attribution {
// allows comments as much as you like
name: "Foobar"
files: ["some/file.h", "some/file.cpp"]
license: License.GPL // can be a QML enum in a License.qml
// ...
}
That would be all nicely human-readable and easily verified with
qmllint. I get the argument for sticking with JSON now, though.
best,
Ulf
--
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development
