all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Christopher Baines <mail@cbaines.net>
Cc: 39142@debbugs.gnu.org, pelzflorian@pelzflorian.de
Subject: [bug#39142] Update USB_ModeSwitch.
Date: Sun, 19 Jan 2020 11:11:29 +0100	[thread overview]
Message-ID: <20200119111129.48f3eaa3@scratchpost.org> (raw)
In-Reply-To: <87r1zxotuh.fsf@cbaines.net>

[-- Attachment #1: Type: text/plain, Size: 1420 bytes --]

Hi,

On Sat, 18 Jan 2020 12:02:46 +0000
Christopher Baines <mail@cbaines.net> wrote:

> > 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?

Yes, on that ".../compare" page, just like "Version changes" there could be
an always-visible section "License changes".

> 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!

I'm not sure that that could ever be reliably automated (after all, the source
code can say whatever license text in the comments--we can't have an
exhaustive list).

In general it would already be much help to automate basically

  grep -ri 'gnu general' $(grep -ril license .)

just in order to reduce the workload.  But I think we already package third
party license checkers for that, no need to do that for Guix Data Service.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-01-19 10:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-15 12:48 [bug#39142] Update USB_ModeSwitch pelzflorian (Florian Pelz)
2020-01-15 12:50 ` [bug#39142] [PATCH 1/2] gnu: USB_ModeSwitch: Update to 2.6.0 Florian Pelz
2020-01-15 12:50 ` [bug#39142] [PATCH 2/2] gnu: USB_ModeSwitch data: Update to 20191128 Florian Pelz
2020-01-18 11:29 ` [bug#39142] Update USB_ModeSwitch Christopher Baines
2020-01-18 11:52   ` Danny Milosavljevic
2020-01-18 12:02     ` Christopher Baines
2020-01-19 10:11       ` Danny Milosavljevic [this message]
2020-01-20  9:03   ` bug#39142: " pelzflorian (Florian Pelz)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200119111129.48f3eaa3@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=39142@debbugs.gnu.org \
    --cc=mail@cbaines.net \
    --cc=pelzflorian@pelzflorian.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.