Bob and Mary, I was aware that reanalysis was not performed on duplicate files --- but how do we present the data so that the user isn't tracking down the same files that have been 'flagged' with a license.
It looks like v 1.2 will indicate if there are license changes from one upload of the same file(s) to the next? I must have missed that in the features list.... how will it be reported? ---- or is there a mockup screenshot of this capability? ------- Basically, I just want the user to be able to zero in on the changes from the last upload relative to detected licenses. thanks Tom Murray Bob Gobeille <[email protected]> 08/13/2009 12:56 PM To "[email protected]" <[email protected]> cc [email protected] Subject Re: [FOSSology] Handling duplicate files from multiple uploads.... On Aug 13, 2009, at 10:45 AM, [email protected] wrote: We would like our product teams to submit their source code for open source analysis at periodic times throughout the development cycle (at least once per year for active projects). Most likely they will create a .tar for their source code directory and upload to our fossology server. We would like to avoid re-analyzing and reporting files that have already been reported from earlier runs. Can you recommended a method for handling this situation without burdening the product development teams too much (i.e. so they don't have to keep track of the files and somehow filter them for subsequent runs)? Hi Tom, I just wrote (yesterday) the sql to do this in v 1.2. Take two uploads - report the license changes. Bob Gobeille [email protected]
_______________________________________________ fossology mailing list [email protected] http://fossology.org/mailman/listinfo/fossology
