1 |
On Thu, Jan 3, 2013 at 9:39 AM, Ulrich Mueller <ulm@g.o> wrote: |
2 |
> We could easily solve this by adding a "binary-only" or |
3 |
> "no-source-code" tag to such packages. It would be included in the |
4 |
> @BINARY-REDISTRIBUTABLE license group, but not in @FREE. So such |
5 |
> packages would be excluded for users with ACCEPT_LICENSE="-* @FREE". |
6 |
|
7 |
As long as it is also marked with the BSD license I don't have a |
8 |
problem with this. The license is, in fact, BSD, so we do need to |
9 |
keep that info around. |
10 |
|
11 |
> |
12 |
> Thinking about the name, "no-source-code" might be a better choice |
13 |
> than "binary-only". As the GPL defines it, "The source code for a work |
14 |
> means the preferred form of the work for making modifications to it." |
15 |
> This may be binary, e.g. for pictures in a bitmap format. |
16 |
|
17 |
I understand the distinction adds value to our users, but I find it |
18 |
amusing that a computer scientist would even try to define the term |
19 |
"source code." :) |
20 |
|
21 |
Rich |