Danny Milosavljevic <dannym@scratchpost.org> writes:

> Hi,
>
> On Sat, 18 Jan 2020 11:29:41 +0000
> Christopher Baines <mail@cbaines.net> wrote:
>
>> 1: https://guix-patches-data.cbaines.net/compare?base_commit=9edae6c05cd879393d59702f033f4c3ccce30dba&target_commit=0115c829cc1021b01b1686c5d28a7f6004390c83
>
> Very nice!

Thanks :)

> In general, I suggest to also list license changes.  Whether we like it or
> not, in practice those happen and it's important to know (especially to know
> when they stay the same).

So, the Guix Data Service does know what licenses are associated with a
package. I guess it could list packages where that's changed on the main
comparison page, is that what you're referring to?

In my mind at least, the primary issue when reviewing packages is making
sure the license list for the package corresponds with the actual
licenses that apply to the contents. That's a little harder, as you'd
have to download the source tarball, and run licensecheck or something
similar, but hopefully that can be automated at some point!

Chris