From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-dev+bounces-59902-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id C7AD71381F3
for <garchives@archives.gentoo.org>; Fri, 26 Apr 2013 21:23:08 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 0A584E0D0F;
Fri, 26 Apr 2013 21:22:53 +0000 (UTC)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172])
(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 21337E0D0B
for <gentoo-dev@lists.gentoo.org>; Fri, 26 Apr 2013 21:22:51 +0000 (UTC)
Received: by mail-vc0-f172.google.com with SMTP id hx10so4179697vcb.17
for <gentoo-dev@lists.gentoo.org>; Fri, 26 Apr 2013 14:22:51 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=mime-version:x-received:sender:x-originating-ip:in-reply-to
:references:date:x-google-sender-auth:message-id:subject:from:to
:content-type:x-gm-message-state;
bh=wFT69q6QKsM7vKHpxpRrfcsW6Vf0yDEg6hXEwiE7aW4=;
b=fxSiImQmmx7U7KMLN9EtczcDz1S2pXMtJU6ty4PCllP3qsXHrnUCuMa85Ou3Mu2tCP
/5s9v3nDeuRpGqIg2k4CaRWZ64iLaoSttzY7tswCuovAvxGqpboCEFDxSAE11boip2Yb
BJSDaNtEB4+jurJDDWhZG0X18iQO3dgY0ehE3UtM4pFqCNcuRL1SJQvMdteMgdyRmKG4
AXvnJGA3cgghOvPBH9HsUNbXTjNPxwsHyMpbNbT4DOADW/pOnVjqDkiuRF2QRCTsH5zT
AquDKkufHYZMMo5WKj5NJhjrpdFkBLNQgAre5BA73KBjk/6V9SClOy36mgr6GsVO/frr
ZGmA==
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
X-Received: by 10.221.0.199 with SMTP id nn7mr29973347vcb.14.1367011371277;
Fri, 26 Apr 2013 14:22:51 -0700 (PDT)
Sender: antarus@scriptkitty.com
Received: by 10.220.40.146 with HTTP; Fri, 26 Apr 2013 14:22:51 -0700 (PDT)
X-Originating-IP: [172.19.14.220]
In-Reply-To: <20858.42422.774640.252393@a1i15.kph.uni-mainz.de>
References: <20858.42422.774640.252393@a1i15.kph.uni-mainz.de>
Date: Fri, 26 Apr 2013 14:22:51 -0700
X-Google-Sender-Auth: dspA8wt1ZUoXoVYij3k1PCSEZGI
Message-ID: <CAAr7Pr_8V8JmdF8jKtg6fn6OAUd-vgiPfbSu5LiHP2+SyJQEtA@mail.gmail.com>
Subject: Re: [gentoo-dev] Should mirror restriction imply bindist restriction?
From: Alec Warner <antarus@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Content-Type: multipart/alternative; boundary=bcaec54eea8a3073db04db4a2382
X-Gm-Message-State: ALoCoQkLixN8vy2SQGnNX38OHxKcS+rBfws/Zb+QzN9B2GlGyRx+jFjfkujLfRDtIslMJc/rLEsr
X-Archives-Salt: 883515ec-0d79-478f-92af-4f1733515391
X-Archives-Hash: 304361158a2bb19349a62fad974bd6c1
--bcaec54eea8a3073db04db4a2382
Content-Type: text/plain; charset=UTF-8
So years ago, we had GRP (the Gentoo Reference Platform.) My understanding
of USE=bindist was that when building packages whose binaries were illegal
to distribute, the build system would take some action. For instance, for a
while we were not allowed to brand a source build of firefox as firefox, so
debian made iceweasel and we ourselves add USE=bindist so we could build
custom builds and replacing the branding.
I'm not sure RESTRICT=bindist actually does anything. My guess is that the
intention of the restriction is to warn users that when building binaries
packages of a given package, there are 'legal issues' with such
distribution. That being said, as some have noted in the thread, the legal
issues are diverse and are unlikely to be covered in one flag.
-A
On Fri, Apr 26, 2013 at 9:05 AM, Ulrich Mueller <ulm@gentoo.org> wrote:
> Currently RESTRICT=mirror and RESTRICT=bindist are independent of each
> other. I wonder if the former should imply the latter.
>
> Is there any package where the files in SRC_URI cannot be mirrored
> (i.e., redistributed), but where the built package can be distributed?
>
> Ulrich
>
>
--bcaec54eea8a3073db04db4a2382
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">So years ago, we had GRP (the Gentoo Reference Platform.) =
My understanding of USE=3Dbindist was that when building packages whose bin=
aries were illegal to distribute, the build system would take some action. =
For instance, for a while we were not allowed to brand a source build of fi=
refox as firefox, so debian made iceweasel and we ourselves add USE=3Dbindi=
st so we could build custom builds and replacing the branding.<div>
<br></div><div style>I'm not sure RESTRICT=3Dbindist actually does anyt=
hing. My guess is that the intention of the restriction is to warn users th=
at when building binaries packages of a given package, there are 'legal=
issues' with such distribution. That being said, as some have noted in=
the thread, the legal issues are diverse and are unlikely to be covered in=
one flag.</div>
<div style><br></div><div style>-A</div></div><div class=3D"gmail_extra"><b=
r><br><div class=3D"gmail_quote">On Fri, Apr 26, 2013 at 9:05 AM, Ulrich Mu=
eller <span dir=3D"ltr"><<a href=3D"mailto:ulm@gentoo.org" target=3D"_bl=
ank">ulm@gentoo.org</a>></span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Currently RESTRICT=3Dmirror and RESTRICT=3Db=
indist are independent of each<br>
other. I wonder if the former should imply the latter.<br>
<br>
Is there any package where the files in SRC_URI cannot be mirrored<br>
(i.e., redistributed), but where the built package can be distributed?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Ulrich<br>
<br>
</font></span></blockquote></div><br></div>
--bcaec54eea8a3073db04db4a2382--