This thread has died down a bit, but I don’t think we came to any real
consensus, so I going to attempt to get some consensus.
I think we have a need for two things: the ability to store serial numbers
for a server and the ability to store “notes” for a server.
The way I see it there are two ways (
Given only two options I'd go for the second one. We shouldn't be afraid to
model our data in a database, especially since we're the driving force between
every supported application that touches it. Adding more logic and safeties
inside the TO API is just reimplementing the job that a databas
Hi, all.. I think weasel is mature enough that it covers our license
usage well enough. RAT is run as a separate job from the rpm builds and
runs on the source tarball; weasel runs during the build process on the
source cloned from github:they have pretty much the same function, but
use
Is Rat providing license checking that is not covered by Weasel? What are
we losing but no longer using Rat?
On Mon, Nov 26, 2018 at 2:47 PM Dan Kirkwood wrote:
> Hi, all.. I think weasel is mature enough that it covers our license
> usage well enough. RAT is run as a separate job from th
Rat does do a few things that weasel doesn't:
- It has a lower false positive license rate; it is much less likely
to falsely identify a project as having a particular license and
instead produce an Unknown.
- It has better support for checking to ensure that a file has the
appropriate Apache hea
