RFC Automatically produce legal compliance info

Quoted 13 lines

However, I can see something missing for GPL/LGPL packages. GPL/LGPL states that you must also provide "the scripts used to control compilation and installation of the executable."

Which means that, for packages such as Linux, busybox and uClibc (maybe others as well), the associated .config file should be bundled as well.

Also, the config/build/install instructions for each GPL/LGPL package must be provided. This could probably be done by bundling the buildroot sources too in output/legal-info/sources/, or by leveraging the package infrastructure to output the executed commands for every packages.

Quoted 5 lines

Also, for packages that get patches applied by buildroot, you must make sure that the tarballs for those packages do contain the pathced code, or that the patches are bundled as well. From what I see, you currently only copy the downladed tarballs. Of course, if buildroot is also copied to the output/legal-info/sources/ the patches will be there.

I agree with Yann: I think we should package buildroot itself as well.

In fact, I think we should:
- make distclean
- create the manifest
- download all needed sources
- run a pre-legal-package script for customization
- create a .tar file with the whole

The pre-legal-package script (whatever the name) is similar to the post-build script, and allows projects to modify certain things. For example, modify the defconfig to disable some proprietary things that are not useful or usable by the customer.

Also, I think the DL_DIR setting should be modified so that it points to the location where the source tarballs are downloaded. This way, the customer can directly use these sources from that location when re-building buildroot.

I haven't done a technical review of your patches, but I went through them and agree with the principle. Thanks for posting them before the developer day, it will certainly help the discussion!