On Sat, Oct 24, 2009 at 8:11 AM, Vagrant Cascadian <vagrant+g...@freegeek.org> wrote: > i've been working on packaging gPXE for Debian, but in order to get proper > inclusion, it needs an exhaustive license and copyright review. > > it seems like there's a mechanism for (i forget the exact syntax): > > make -C src FOO.rom.licence > > but this has to be done for each and every rom separately, or is there a way > to > review the whole codebase with a single command? any other suggestions on how > to work with gPXE developers on these issues?
I don't think there is a way to build a gPXE image that contains all features at once(think of BIOS and EFI support at the same time). > as an alternate auditing mechanism, i've used licensecheck (from the > devscripts > package in debian) and manually deleted the ones that seem mostly ok, to > produces the attached list of files that need further review. licensecheck > parses the contents of the files themselves, looking for known licensing and > copyright patterns. licensecheck will likely come up with a little different > set of issues than the make *.licence checks. There is a FILE_LICENCE() macro at the top of every file in src/. You can grep all files for FILE_LICENCE() and put the output into a file. Remove all the known-good ones and see if something is left in the list. The FILE_LICENCE macro is also the source of information for 'make bin/foo.rom.licence'. Thomas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
