From: Michael Weber <xmw@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Should mirror restriction imply bindist restriction?
Date: Fri, 26 Apr 2013 21:55:04 +0200 [thread overview]
Message-ID: <517ADB98.9020403@gentoo.org> (raw)
In-Reply-To: <20858.54334.173774.722711@a1i15.kph.uni-mainz.de>
On 04/26/2013 09:23 PM, Ulrich Mueller wrote:
>>>>>> On Fri, 26 Apr 2013, Mike Frysinger 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?
>
>> i've used RESTRICT=mirror in the past when the files were really
>> large (like games or toolchain source tarballs) and upstream already
>> had a good mirroring system. in both cases, there was no binary
>> redistribution restrictions.
>
>> so my answer would be no: we have two independent knobs and let's
>> keep them that way.
>
> Right. And as was pointed to me on IRC, another legitimate case for
> mirror restriction are packages in overlays whose distfiles are not on
> mirrors. Then it obviously makes no sense to check mirrors for it.
And sunrise suggested to not set it, to make the move into main tree
less error prone.
I think, all the legal terms "no mirror" and "no branded redistribution"
are clear, but portage might get problems to check/recognise "within a
legal entity". DNS zones, netblocks and so on are all optional and do
not necessarily represent these boundaries.
trusted computing platform ... please no.
GPG keys sets with encrypted tarballs would raise the awareness, all of
them bypass-able
In the end, legally speaking, it's the user pushing buttons and portage
is no licensed lawyer.
Michael
--
Michael Weber
Gentoo Developer
web: https://xmw.de/
mailto: Michael Weber <xmw@gentoo.org>
next prev parent reply other threads:[~2013-04-26 19:55 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 [this message]
2013-04-26 19:57 ` Mike Frysinger
2013-04-26 21:22 ` Alec Warner
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=517ADB98.9020403@gentoo.org \
--to=xmw@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