>It would be great if the indent width of comment replies were halved so that it would take twice as long for this to happen

Seconded.

>I'm not sure exactly what the output should look like since I can't find sample usage anywhere, but I would have expected to get a list of source code files that contain blobs.

I'm not sure, but I think that's what the script is trying to give based on any license declarations it finds in the files. The WHENCE file it lists, for example, doesn't contain a full license declaration and so is marked as non-free; the HEX, ihex, and H16 files you mention seem to (in most cases) contain GPLv2 declarations at the bottom. I don't know if these are actually legal, but they're there.

It appears that this script won't be much help. Hopefully the other scripts in the set are slightly more effective.

>Looking through the files manually it appears that almost everything in /firmware/ has to go. It's all .HEX, .ihex, or .H16 files with no actual source code.

It appears so. Have you tried the deblob-main script? Apparently that should deblob tarballs, although the performance of deblob-check suggests manual cleansing might be needed.

Reply via email to