From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:49529) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1it7Yp-0001Mh-Hr for guix-patches@gnu.org; Sun, 19 Jan 2020 05:12:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1it7Yo-0003vO-7p for guix-patches@gnu.org; Sun, 19 Jan 2020 05:12:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:36651) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1it7Yo-0003vE-4u for guix-patches@gnu.org; Sun, 19 Jan 2020 05:12:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1it7Yn-0001Ta-Vm for guix-patches@gnu.org; Sun, 19 Jan 2020 05:12:01 -0500 Subject: [bug#39142] Update USB_ModeSwitch. Resent-Message-ID: Date: Sun, 19 Jan 2020 11:11:29 +0100 From: Danny Milosavljevic Message-ID: <20200119111129.48f3eaa3@scratchpost.org> In-Reply-To: <87r1zxotuh.fsf@cbaines.net> References: <20200115124810.j3myokleoa7le3sq@pelzflorian.localdomain> <87sgkdovdm.fsf@cbaines.net> <20200118125238.3423c25d@scratchpost.org> <87r1zxotuh.fsf@cbaines.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_/fVghyVtP_/x67Pbmws8L9Lt"; protocol="application/pgp-signature"; micalg=pgp-sha256 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Christopher Baines Cc: 39142@debbugs.gnu.org, pelzflorian@pelzflorian.de --Sig_/fVghyVtP_/x67Pbmws8L9Lt Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Hi, On Sat, 18 Jan 2020 12:02:46 +0000 Christopher Baines 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). =20 >=20 > 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 sou= rce 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. --Sig_/fVghyVtP_/x67Pbmws8L9Lt Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEds7GsXJ0tGXALbPZ5xo1VCwwuqUFAl4kK1EACgkQ5xo1VCww uqVRYwgAiok6svZdsi1bfimftZTMZtLBuuWgWbw6VOI+ucEwBx/SUhbZcNo2Eo4d eI7h0ekuIeDAXm9RFEPjwMTshRNUko5HlH16uIm/1ZjSSUWi1Pf4bQdNOi5m1hIK HTUxgCH9wNXewxtWqx+ySBzS3b9OOs+FWg0yxuCcRjF4BdmKcCcO7aMgeAd58ZLE Ax8q1zApqpcPUyA4l0qC4heh0Xa1MyhNu8dW74AeIwctcJAoPJyrX8zs7M+9pJC7 wbcrtD/sKfsHxpA7cGJbSbstmeTkgGw72HpapWOnHbw/I2IJcPzjNH3Btohcbsh2 3z2mDBaQp324yhIpX/nJMsPY/dYQgg== =zPj2 -----END PGP SIGNATURE----- --Sig_/fVghyVtP_/x67Pbmws8L9Lt--