| 1 |
On Wed, Feb 25, 2015 at 1:38 PM, Mike Gilbert <floppym@g.o> wrote: |
| 2 |
> |
| 3 |
> |
| 4 |
> I would like to remove the elog for a couple of reasons: |
| 5 |
> |
| 6 |
> 1. The use flag description is there for whoever cares to read it. |
| 7 |
> There is no need to alert the user every time. |
| 8 |
> 2. We are not lawyers, and I have no business giving legal advice |
| 9 |
> about patent law which varies from country to country. |
| 10 |
> |
| 11 |
> To take it one step further: I think it would make more sense to call |
| 12 |
> the flag "h264" or something similar. We could then set |
| 13 |
> RESTRICT="h264? ( bindist )" if we want to give some indication that |
| 14 |
> it is not appropriate for binary redistribution. |
| 15 |
> |
| 16 |
> What you're saying here makes sense and I agree, but our users are already |
| 17 |
pretty confused about USE=bindist... what it does, why it's enabled by |
| 18 |
default, etc. If this is going to stay enabled by default in our stage3s |
| 19 |
(there's an open bug about possibly changing that) then I really think we |
| 20 |
should add a paragraph to the handbook that explains things. |
| 21 |
|
| 22 |
It seems that most new users don't have any idea what bindist is until they |
| 23 |
find some feature missing or they hit the classic openssl/openssh blocker |
| 24 |
and someone has to explain the whole thing to them. |
| 25 |
|
| 26 |
So in summary, let's get rid of the per-ebuild einfo warnings but let's |
| 27 |
educate the users about USE=bindist earlier. |
| 28 |
|
| 29 |
-Ben |
Archives