[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] do we need special elog messages for bindist?
From:       Ben Kohler <bkohler () gmail ! com>
Date:       2015-02-25 20:04:48
Message-ID: CANSUr=J74N9hZWZL95BPQptrUNDxCBLU0ZAdNNxq7nwP7AMqRA () mail ! gmail ! com
[Download RAW message or body]

On Wed, Feb 25, 2015 at 1:38 PM, Mike Gilbert <floppym@gentoo.org> wrote:
>
>
> I would like to remove the elog for a couple of reasons:
>
> 1. The use flag description is there for whoever cares to read it.
> There is no need to alert the user every time.
> 2. We are not lawyers, and I have no business giving legal advice
> about patent law which varies from country to country.
>
> To take it one step further: I think it would make more sense to call
> the flag "h264" or something similar. We could then set
> RESTRICT="h264? ( bindist )" if we want to give some indication that
> it is not appropriate for binary redistribution.
>
> What you're saying here makes sense and I agree, but our users are already
pretty confused about USE=bindist... what it does, why it's enabled by
default, etc.  If this is going to stay enabled by default in our stage3s
(there's an open bug about possibly changing that) then I really think we
should add a paragraph to the handbook that explains things.

It seems that most new users don't have any idea what bindist is until they
find some feature missing or they hit the classic openssl/openssh blocker
and someone has to explain the whole thing to them.

So in summary, let's get rid of the per-ebuild einfo warnings but let's
educate the users about USE=bindist earlier.

-Ben

[Attachment #3 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Feb 25, 2015 \
at 1:38 PM, Mike Gilbert <span dir="ltr">&lt;<a href="mailto:floppym@gentoo.org" \
target="_blank">floppym@gentoo.org</a>&gt;</span> wrote:<blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div><div> <br>
</div></div>I would like to remove the elog for a couple of reasons:<br>
<br>
1. The use flag description is there for whoever cares to read it.<br>
There is no need to alert the user every time.<br>
2. We are not lawyers, and I have no business giving legal advice<br>
about patent law which varies from country to country.<br>
<br>
To take it one step further: I think it would make more sense to call<br>
the flag &quot;h264&quot; or something similar. We could then set<br>
RESTRICT=&quot;h264? ( bindist )&quot; if we want to give some indication that<br>
it is not appropriate for binary redistribution.<br>
<br>
</blockquote></div>What you&#39;re saying here makes sense and I agree, but our users \
are already pretty confused about USE=bindist... what it does, why it&#39;s enabled \
by default, etc.   If this is going to stay enabled by default in our stage3s \
(there&#39;s an open bug about possibly changing that) then I really think we should \
add a paragraph to the handbook that explains things.</div><div \
class="gmail_extra"><br></div><div class="gmail_extra">It seems that most new users \
don&#39;t have any idea what bindist is until they find some feature missing or they \
hit the classic openssl/openssh blocker and someone has to explain the whole thing to \
them.</div><div class="gmail_extra"><br></div><div class="gmail_extra">So in summary, \
let&#39;s get rid of the per-ebuild einfo warnings but let&#39;s educate the users \
about USE=bindist earlier.</div><div class="gmail_extra"><br></div><div \
class="gmail_extra">-Ben</div></div>



[prev in list] [next in list] [prev in thread] [next in thread]