Re: [go-nuts] using or extending or forking+renaming github.com/google/licensecheck to provide similar functionality

2019-11-14 Thread fgergo
Sorry I did not read your response fully. Repeating the matching is just fine. Thanks again! On Thu, Nov 14, 2019 at 10:56 AM wrote: > > Thanks, I did not realize that Coverage -> Match[n] could be that useful! > Though the field Match.Name is not a file name I can os.Open(). > How can I directly

Re: [go-nuts] using or extending or forking+renaming github.com/google/licensecheck to provide similar functionality

2019-11-14 Thread fgergo
Thanks, I did not realize that Coverage -> Match[n] could be that useful! Though the field Match.Name is not a file name I can os.Open(). How can I directly access the known license texts? On Thu, Nov 14, 2019 at 10:42 AM Dan Kortschak wrote: > > The licensecheck.Match type holds the start and e

Re: [go-nuts] using or extending or forking+renaming github.com/google/licensecheck to provide similar functionality

2019-11-14 Thread Dan Kortschak
The licensecheck.Match type holds the start and end offsets in the file. Can't you use that to extract the license portion and either check it's length against the length of the license or repeat the Check with only that portion of the file? On Thu, 2019-11-14 at 10:24 +0100, fge...@gmail.com wrot

Re: [go-nuts] using or extending or forking+renaming github.com/google/licensecheck to provide similar functionality

2019-11-14 Thread fgergo
Sorry if I was not clear: on walking the file system, that's clear, I did not intend to talk about that, only about matching and reporting on matching. The example I gave was just to put in context why I believe I'd need a different api. Using the Options field is good enough in the first example.

Re: [go-nuts] using or extending or forking+renaming github.com/google/licensecheck to provide similar functionality

2019-11-14 Thread Rob Pike
As I understand what you're trying to do, you just need to write a tree walker, perhaps using filepath.Walk, that opens each file and calls Cover on it. You can set the Options field to control the threshold for reporting, and use the result of that to choose which licenses to report. I don't beli

Re: [go-nuts] using or extending or forking+renaming github.com/google/licensecheck to provide similar functionality

2019-11-13 Thread fgergo
func Cover(input []byte, opts Options) (Coverage, bool) in licensecheck currently reports len(input)/len(one of the licenses) for each known license. I'd need for all known licenses len(known license)/len(license reference in input). I'd like to scan >10 files (possibly a lot more), where some

Re: [go-nuts] using or extending or forking+renaming github.com/google/licensecheck to provide similar functionality

2019-11-13 Thread Rob Pike
Can you please explain in more detail what you're asking for? I don't understand the problem you have or why the current package cannot handle it. -rob On Wed, Nov 13, 2019 at 7:05 PM wrote: > Hi, > > "licensecheck classifies license files and heuristically determines > how well they correspo

[go-nuts] using or extending or forking+renaming github.com/google/licensecheck to provide similar functionality

2019-11-13 Thread fgergo
Hi, "licensecheck classifies license files and heuristically determines how well they correspond to known open source licenses." I'd like to identify license references in the file system. If I understand correctly package licensecheck in it's current form is not useful to help with this. If it'