From: Alec Warner <antarus@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Should mirror restriction imply bindist restriction?
Date: Fri, 26 Apr 2013 14:22:51 -0700 [thread overview]
Message-ID: <CAAr7Pr_8V8JmdF8jKtg6fn6OAUd-vgiPfbSu5LiHP2+SyJQEtA@mail.gmail.com> (raw)
In-Reply-To: <20858.42422.774640.252393@a1i15.kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
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
>
>
[-- Attachment #2: Type: text/html, Size: 1595 bytes --]
prev parent reply other threads:[~2013-04-26 21:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 16:05 [gentoo-dev] Should mirror restriction imply bindist restriction? Ulrich Mueller
2013-04-26 16:15 ` Peter Stuge
2013-04-26 16:21 ` Rick "Zero_Chaos" Farina
2013-04-26 16:56 ` Jeroen Roovers
2013-04-26 17:14 ` Rick "Zero_Chaos" Farina
2013-04-26 17:15 ` Jeroen Roovers
2013-04-26 18:30 ` Rick "Zero_Chaos" Farina
2013-04-26 18:44 ` Rich Freeman
2013-04-26 19:07 ` Rick "Zero_Chaos" Farina
2013-04-26 19:24 ` Ian Stakenvicius
2013-04-26 19:35 ` Rich Freeman
2013-04-26 19:43 ` Rick "Zero_Chaos" Farina
2013-04-26 19:53 ` Rich Freeman
2013-04-26 17:19 ` Chí-Thanh Christopher Nguyễn
2013-04-26 21:40 ` [gentoo-dev] " Duncan
2013-04-26 18:52 ` [gentoo-dev] " Mike Frysinger
2013-04-26 19:23 ` Ulrich Mueller
2013-04-26 19:55 ` Michael Weber
2013-04-26 19:57 ` Mike Frysinger
2013-04-26 21:22 ` Alec Warner [this message]
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=CAAr7Pr_8V8JmdF8jKtg6fn6OAUd-vgiPfbSu5LiHP2+SyJQEtA@mail.gmail.com \
--to=antarus@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox