From: Rich Freeman <rich0@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 15:35:00 -0400 [thread overview]
Message-ID: <CAGfcS_mD6dqkN79Qf6VYvFbkwqUFdLt-re1tb9NQypmYAaOvjg@mail.gmail.com> (raw)
In-Reply-To: <517AD45B.6070800@gentoo.org>
On Fri, Apr 26, 2013 at 3:24 PM, Ian Stakenvicius <axs@gentoo.org> wrote:
> IUSE="bindist" tends to be for adjusting a particular package so that
> it either is generic and CAN be binary-distributable, or will build as
> upstream intended (with, for instance, upstream branding) and
> therefore is not. Right?
Correct.
>
> So, in essence, the use flag can allow for an exception of a 'bindist'
> LICENSE. Would it make more sense then to have LICENSE= contents
> controlled conditionally? ie:
>
I'm not sure if this is really necessary.
If a user doesn't want to accidentally install something that isn't
redistributable they can start with
ACCEPT_LICENSE=@BINARY-REDISTRIBUTABLE, which already exists.
Then they can augment that by manually overriding it for packages
where they've decided they're not impacted, or where they're using
USE=-bindist.
There are really only a small number of situations where this will
happen. I'm not sure if we need to implement conditional licensing
with a pseudo-license on top of that just to cover them. The license
itself doesn't actually change when you USE -bindist - you're simply
complying with it.
Rich
next prev parent reply other threads:[~2013-04-26 19:35 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 [this message]
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
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=CAGfcS_mD6dqkN79Qf6VYvFbkwqUFdLt-re1tb9NQypmYAaOvjg@mail.gmail.com \
--to=rich0@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