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)?
Thanks, Tom Murray
_______________________________________________ fossology mailing list [email protected] http://fossology.org/mailman/listinfo/fossology
