Hi, On Thu, Aug 30, 2018 at 08:35:19AM +0000, Alm, Michael wrote: > currently I'm struggling with our legal department around the license report > automatically generated by ptxdist. During that process we stumbled upon an > ambiguity. Let me illustrate the problem using the kernel as an example, but > it applies to other packages, as well. > > In the license report, for the kernel it says the name, version, license > [identifier], url, md5 and the license text. The reader gets the impression > that this specific kernel version, based on the sources specified via the > url, is used in the image/product. But actually it's not! Actually the kernel > sources are modified using the patches before building. > > The license (GPLv2) requires us to state, that we modified the kernel. > Furthermore, it requires us to state what these modifications are. Therefore > we would like to provide a list of all the patches applied to the kernel (and > other packages of course) in the respective package section in the license > report. We believe it would be sufficient, to state the names of the patches, > without complete path or content. > > Is there a way to achieve that currently with ptxdist? > If not, do you think it is possible at all? > Does anybody out there on the mailing list have a solution for that?
Take a look at scripts/lib/ptxd_make_world_license.sh. You can overwrite the individual functions in the BSP. I guess you will need to change the generated latex code to include the series file or something like that. Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ ptxdist mailing list [email protected]
