Gentoo Archives: gentoo-dev

From: Chris Gianelloni <wolf31o2@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] ACCEPT_LICENSE revisited
Date: Tue, 21 Nov 2006 14:43:15
Message-Id: 1164120522.10030.15.camel@inertia.twi-31o2.org
In Reply to: Re: [gentoo-dev] ACCEPT_LICENSE revisited by Brian Harring
1 On Mon, 2006-11-20 at 18:28 -0800, Brian Harring wrote:
2 > I as an admin, set ACCEPT_LICENSE=RTCW-ETEULA; now if a user I've
3 > granted sudo to, goes and merges enemy-territory, have they
4 > explicitly agreed to the license? Note the 'explicit', not 'implicit'
5 > as the glep throws around.
6
7 You, as the admin, did *explicitly* accept the license by adding it.
8
9 > Meaning the check_license interactive crap still is required. Hell,
10 > your example in bug 152593, RTCW-ETEULA requires
11
12 Sure.
13
14 > "YOU ACKNOWLEDGE THAT YOU HAVE READ THIS AGREEMENT, YOU UNDERSTAND
15 > THIS AGREEMENT, AND UNDERSTAND THAT BY CONTINUING THE DOWNLOAD OR
16 > INSTALLATION OF THE SOFTWARE, BY LOADING OR RUNNING THE SOFTWARE, OR
17
18 Downloading and installing... that's what we cover.
19
20 As for *running* the software, Gentoo is not responsible for what a user
21 does on their own system. We are responsible for the downloading and
22 installing, which is the part that we do. Sure, it could be argued that
23 *we* don't do anything, since it isn't us typing "emerge
24 enemy-territory" but trying to cover ourselves is a good idea.
25
26 > BY PLACING OR COPYING THE SOFTWARE ONTO YOUR COMPUTER HARD DRIVE OR
27 > RAM, YOU AGREE TO BE BOUND BY THE TERMS AND CONDITIONS OF THIS
28 > AGREEMENT. YOU FURTHER AGREE THAT, EXCEPT FOR WRITTEN SEPARATE
29 > AGREEMENTS, IF ANY, BETWEEN ID AND YOU, THIS AGREEMENT IS A
30 > COMPLETE AND EXCLUSIVE STATEMENT OF THE RIGHTS AND LIABILITIES OF THE
31 > PARTIES HERETO, RELATING TO THE SUBJECT MATTER HEREOF. THIS AGREEMENT
32 > SUPERSEDES ALL PRIOR ORAL AGREEMENTS, PROPOSALS OR UNDERSTANDINGS, AND
33 > ANY OTHER COMMUNICATIONS, IF ANY, BETWEEN ID AND YOU RELATING TO THE
34 > SUBJECT MATTER OF THIS AGREEMENT."
35 >
36 > Read that again. It requires that anyone even *using* the software
37 > has to have read the agreement, meaning that anyone merging it still
38 > needs to see the license (and have time to at the very least read it
39 > through, technically that in a multi-user setup any user able to even
40 > access that software has to be forced through agreement to the
41 > license.
42
43 Yes, and Gentoo has nothing to do with people *using* software. We are
44 responsible for the downloading and installing.
45
46 How about this, instead? Have you ever installed Enemy Territory
47 *without* using portage?
48
49 Try it. Guess what? You will get the EULA acceptance exactly *once*
50 during the installation, and never again. Now, try running the game as
51 a second user. You didn't have to accept anything, at all. Hell, you
52 don't have to accept anything to download Enemy Territory. Id assumes
53 that by "continuing to download" that you accept the license. That's
54 pretty implicit, isn't it?
55
56 For those of us doomed to repeat history, you will know that I had a
57 *very* lengthy discussion with several people from Id Software back in
58 2003 about exactly this thing. Their response was pretty simple, so
59 long as we duplicated the functionality that was provided by the
60 installer itself, we were fine. Now, I even clarified that by
61 explicitly spelling out how it would work. They understood
62 ACCEPT_LICENSE and agreed that since it was *not* automatic, as a person
63 who was responsible for the system was required to add the license to
64 that variable, that they were *EXPLICITLY* accepting the license to do
65 so.
66
67 > ACCEPT_LICENSE does *not* put us in the legal clear as you claim in
68 > comment #15, matter of fact tend to think it makes things worse since
69 > the setup assumes that one user setting ACCEPT_LICENSE is binding for
70 > all which is not a gurantee that can be made when it comes to the
71 > wording of all licenses.
72
73 It does with Id Software, which is the only company who has ever made
74 any sort of complaint, which is what brought about check_license in the
75 first place. I have since extended that same usage to other company's
76 products that the license text said required it, even though they never
77 asked us to do any such thing, simply to avert any possible problems in
78 the future.
79
80 > unix does, and if ACCEPT_LICENSE set by some random user is able to
81
82 It isn't "some random user" at all. It is the system administrator.
83 The one (or ones) responsible for such acceptance. Again, *Gentoo* is
84 only liable for the downloading and installing, and not the execution.
85
86 > > Certain packages will *always* require interactive acceptance of the
87 > > license, as they currently do.
88 >
89 > Certain licenses, not packages. It's possible for a package to be
90 > available under dual licenses, one requiring click through, one not;
91 > sounds daft, but it's possible since LICENSE depset supports use
92 > conditionals/flags. Terminology mind you, but folks get confused
93 > (right marius?).
94
95 Uhhh... no. What I said was correct. Certain *packages* require
96 acceptance of their license.
97
98 --
99 Chris Gianelloni
100 Release Engineering Strategic Lead
101 Alpha/AMD64/x86 Architecture Teams
102 Games Developer/Council Member/Foundation Trustee
103 Gentoo Foundation

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-dev] ACCEPT_LICENSE revisited Stuart Herbert <stuart.herbert@×××××.com>
Re: [gentoo-dev] ACCEPT_LICENSE revisited "Kevin F. Quinn" <kevquinn@g.o>