1 |
On Mon, Dec 28, 2009 at 12:36:34AM -0500, Vincent Launchbury wrote: |
2 |
> 1) Not all of the licenses are completely accurate. For example, the |
3 |
> Linux kernels are listed as soley GPL-2, yet they contain blobs of |
4 |
> non-free firmware. Perhaps a general-purpose "not-free" license could be |
5 |
> appended to such packages. This would only affect people who choose to |
6 |
> use the feature. It could be minused from the FSF-APPROVED group for |
7 |
> example. |
8 |
Actually, this is a case where the license on the ebuild is wrong, not |
9 |
the license group. The kernel ebuilds should have GPL-2 and something |
10 |
else, and by definition should not pass @FSF-APPROVED alone. |
11 |
|
12 |
> Also relating to this, what is freedist? The package app-text/dos2unix |
13 |
> lists 'freedist' as its license, and /usr/portage/licenses/freedist says |
14 |
> only "Freely Distributable". Several other packages do this, and I'm |
15 |
> sure it's not correct. I'm not entirely sure, but I think the dos2unix |
16 |
> package is from http://www.thefreecountry.com/tofrodos/, which clearly |
17 |
> says its GPLv2. Packages like this could be looked into and fixed. |
18 |
tofrodos is NOT dos2unix. If you compare the sources you'll see they are |
19 |
radically different. |
20 |
|
21 |
The COPYRIGHT file in dos2unix is actually a 2-clause BSD license. I've |
22 |
updated the ebuild suitably. |
23 |
|
24 |
Yes, we do definitely need to review licenses on packages where they |
25 |
aren't clear, correct any mistakes. |
26 |
|
27 |
> 2) There are no free versions of the kernel in the main tree. The Latin |
28 |
> American FSF maintains blob-free kernels at |
29 |
> http://www.linux-libre.fsfla.org/pub/linux-libre/releases/. They could |
30 |
> be added alongside the official vanilla ebuilds. |
31 |
File a bug with some ebuilds. |
32 |
|
33 |
> 3) Some free software packages bring in non-free optional dependencies |
34 |
> by default. For example, media-gfx/imagemagick brings in |
35 |
> media-fonts/corefonts. As suggested by Sebastian, a free profile could be |
36 |
> created, that changes these defaults, to reduce the hassle of |
37 |
> maintaining a free system. Again, this would only affect users who |
38 |
> choose to use that profile. |
39 |
A profile is not the answer here. |
40 |
An optional DEP block || ( media-fonts/corefonts ... ) where the other |
41 |
item does resolve using ACCEPT_LICENSES is what should be used. |
42 |
|
43 |
In this line of work, we would greatly appreciate bugs being filed for |
44 |
all cases where dependencies are not resolvable with your reasonable |
45 |
ACCEPT_LICENSES setting. |
46 |
|
47 |
> 4) Using something like ACCEPT_LICENSES="-* @FSF-APPROVED" is a good |
48 |
> start, but its quite a hassle to keep checking all the licenses. One |
49 |
> annoyance is packages like sys-devel/gcc. gcc has the libgcc license, |
50 |
> which is just GPLv2+, with some extra permissions granted. Although it's |
51 |
> important to make such a distinction, these extra freedoms are |
52 |
> irrelevant to license filtering. |
53 |
> |
54 |
> I suppose the only feasible way to fix this would be to expand the |
55 |
> license groups in /usr/portage/profiles/license_groups. Would it cause |
56 |
> any problems if they were quite large? |
57 |
No, the file can become a lot larger before any problems come up. |
58 |
I deliberately introduced @BINARY-REDISTRIBUTABLE to help packaging of |
59 |
the 10.x release. They simply set that into their ACCEPT_LICENSES and |
60 |
then we're reasonable set. |
61 |
|
62 |
In your case, I propose that we add one or more stacked groups, with an |
63 |
initial content as such: |
64 |
|
65 |
License group name: LIBRE-FREE |
66 |
Purpose: easily selectable license group for libre-free systems. |
67 |
Initial license group contents: |
68 |
@FSF-APPROVED @GPL-COMPATIBLE @OSI-APPROVED @LIBRE-FREE-1 |
69 |
|
70 |
License group name: LIBRE-FREE-1 |
71 |
Purpose: license group to put additional special-case libre-free |
72 |
licenses in. |
73 |
Initial license group contents: |
74 |
libgcc libstdc++ gcc-runtime-library-exception-3.1 |
75 |
|
76 |
We might be able to merge LIBRE-FREE-1 directly into the LIBRE-FREE |
77 |
entry, the portage folk would be able to answer if there would be a |
78 |
performance benefit to having it split or not. |
79 |
|
80 |
> Another option might be to introduce an optional IS_FREE="yes/no" option |
81 |
> to the ebuild files, which could override the other license settings. |
82 |
No. |
83 |
|
84 |
> 5) Documentation on how to set up and maintain a fully free system could |
85 |
> be added. |
86 |
Under my license_group proposal: |
87 |
# echo 'ACCEPT_LICENSES="-* @LIBRE-FREE"' >>/etc/make.conf |
88 |
done. |
89 |
|
90 |
-- |
91 |
Robin Hugh Johnson |
92 |
Gentoo Linux: Developer, Trustee & Infrastructure Lead |
93 |
E-Mail : robbat2@g.o |
94 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |