Hi, > One option is of course to simply ignore it, i.e. not use it ;-)
I don't think this is a good option ;-) > […] > Now, as I have this can of worms open anyway, what would be the best way > to specify a license tag ? Apparently util-linux is similar to that, its README.licenses says: > Please, check the source code for more details. A license is usually at the > start > of each source file. The rules file simply specifies multiple licenses: > UTIL_LINUX_NG_LICENSE := GPL-2.0, GPL-2.0+, GPL-3.0+, LGPL-2.0+, > BSD-3-Clause, BSD-4-Clause, public_domain > UTIL_LINUX_NG_LICENSE_FILES := \ > > file://Documentation/licenses/COPYING.GPLv2;md5=b234ee4d69f5fce4486a80fdaf4a4263 > \ > > file://Documentation/licenses/COPYING.BSD-3;md5=58dcd8452651fc8b07d1f65ce07ca8af > \ > > file://Documentation/licenses/COPYING.UCB;md5=263860f8968d8bafa5392cab74285262 > \ > > file://Documentation/licenses/COPYING.LGPLv2.1;md5=4fbd65380cdd255951079008b364516c - Roland
signature.asc
Description: OpenPGP digital signature
_______________________________________________ ptxdist mailing list ptxdist@pengutronix.de
