From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 48C48138B2C for ; Wed, 20 Feb 2013 04:43:52 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 55FA821C007; Wed, 20 Feb 2013 04:43:48 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 3F7E8E04C8 for ; Wed, 20 Feb 2013 04:43:47 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id 4972433DE1B for ; Wed, 20 Feb 2013 04:43:46 +0000 (UTC) X-Virus-Scanned: by amavisd-new using ClamAV at gentoo.org X-Spam-Flag: NO X-Spam-Score: -1.634 X-Spam-Level: X-Spam-Status: No, score=-1.634 tagged_above=-999 required=5.5 tests=[AWL=-0.995, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.637, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no Received: from smtp.gentoo.org ([IPv6:::ffff:127.0.0.1]) by localhost (smtp.gentoo.org [IPv6:::ffff:127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z8oHuQx55LM2 for ; Wed, 20 Feb 2013 04:43:40 +0000 (UTC) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 13DB033DD94 for ; Wed, 20 Feb 2013 04:43:39 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1U81X5-0003vg-8x for gentoo-dev@gentoo.org; Wed, 20 Feb 2013 05:43:51 +0100 Received: from ip68-231-22-224.ph.ph.cox.net ([68.231.22.224]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 Feb 2013 05:43:51 +0100 Received: from 1i5t5.duncan by ip68-231-22-224.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 20 Feb 2013 05:43:51 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-dev@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-dev] Re: linux-firmware Date: Wed, 20 Feb 2013 04:43:19 +0000 (UTC) Message-ID: References: <1361020086.1920.51.camel@belkin4> <511F8D2E.1080006@flameeyes.eu> <511F9A9F.8040206@gentoo.org> <511F9ADE.2050503@flameeyes.eu> <20767.41371.270947.851486@a1i15.kph.uni-mainz.de> <5120654B.6050406@gentoo.org> <20768.43798.568305.561675@a1i15.kph.uni-mainz.de> <512389BF.9090504@gentoo.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-22-224.ph.ph.cox.net User-Agent: Pan/0.140 (Chocolate Salty Balls; GIT db8adcf /usr/src/portage/src/egit-src/pan2) X-Archives-Salt: b1b4a11c-1556-444e-a340-4b74d1ba1d0b X-Archives-Hash: 6896180b551f03afcaf388d0e9ccd6cd Rick \"Zero_Chaos\" Farina posted on Tue, 19 Feb 2013 09:18:39 -0500 as excerpted: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 02/17/2013 05:04 AM, Ulrich Mueller wrote: >>>>>>> On Sun, 17 Feb 2013, Rick \"Zero Chaos\" Farina wrote: >> >>> I would be very happy to have the licensing issues fixed, it looks >>> like it won't be fun, however I was originally told that redist was a >>> required right for things to be added to linux-firmware at all so I >>> fear a lot of things may be out of sync in the upstream package. >> >> IIUC, they require new additions to be redistributable, but don't >> remove old images if they're not. Which doesn't make sense. >> >> You should consider mirror restriction for this package. > > I semi-agree with you except for one issue, we are the ones creating > this package. Upstream offers a git repo but no tarball. So if we stop > distributing it then that kinda kills the package. > > Maybe a bug for which firmware are not-redistributable and I can remove > them from our package? I want people to have working systems but > following the law is a bit more important. If all upstream has is a git tarball, what about git-snapshot builds? Use the git2 eclass and set a commit number, thus allowing testing and stabilization of a specific commit, but the checkout would be directly from upstream, so (for the general case, live-image case discussed below) gentoo wouldn't be distributing anything but the ebuild. That /would/ add git as a dep of linux-firmware, however. And if linux- firmware is to be an rdep of the kernel... Also, some people might not want even the git-pak-files containing firmware with some licenses on their system. Is it possible to tell git to only clone/pull specific files in a repo? Of course, if upstream has the repo modularized enough, that may not be an issue either, but I'd guess it'd still be rather complex to setup and test and ebuild designed to work that way. Of course, we'd still be distributing any firmware included in the live- images, but I'm not sure if we include any there or not. If so, then certainly someone would have to go thru that and verify the redistributability of each bit of included firmware. But that's a rather limited special case. But regardless, no upstream tarballs, only a git repo, shouldn't be a problem for mirror-restrict. git2.eclass is already enough to deal with that bit. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman