1 |
On Mon, 2003-09-22 at 08:44, Timothee Besset wrote: |
2 |
> Sigh. Let's go over this a third time. --keep is intended to be used when |
3 |
> it's a matter of fixing up things, not for the everyday user to go with. |
4 |
> The ebuilds should put the .run on the HD, and put a wrapper script called |
5 |
> 'et', which will then spawn the .run the first time it's being called so |
6 |
> the the UI is displayed and the interactive setup executes (including the |
7 |
> EULA prompt). |
8 |
|
9 |
Thanks, anyway. As I have said before, if we do not have control of |
10 |
exactly where the files go, then there is ZERO point in having an ebuild |
11 |
at all, since portage will be unable to track the files. If our package |
12 |
manager cannot track the files, why bother having a "package" at all? |
13 |
|
14 |
The .run files do end up on the user's drive, in |
15 |
/usr/portage/distfiles. What I am attempting to do is to perform the |
16 |
same functions as the scripts within the Makeself archive. I am running |
17 |
into problems because ONLY the gtk version of the installer does not |
18 |
segfault. The command-line portion of loki_setup will suit my needs |
19 |
*perfectly*, but since it segfaults, it is no use to me. |
20 |
|
21 |
It basically boils down to this: if the user can choose where to install |
22 |
the package (versus us telling it where), then it is useless for us to |
23 |
try to create an ebuild for it. |
24 |
|
25 |
> I will update the packages once again to fix that head thing when I find |
26 |
> the time. It might take a week or two. With a wrapper script you can go |
27 |
> around this when you spawn the .run anyway, either by faking a different |
28 |
> head binary, or maybe with the right env vars: |
29 |
> |
30 |
> "For example, if you are running older software that assumes an older |
31 |
> version of POSIX and uses `sort +1', `head -1', or `tail +1', you can work |
32 |
> around the compatibility problems by setting `_POSIX2_VERSION=199209' in |
33 |
> your environment." (I did not verify that this is working, taken from the |
34 |
> docs) |
35 |
> |
36 |
> If that's not good enough, then just remove the files from ebuild. |
37 |
|
38 |
It appears that the only course of action we have left to remain good |
39 |
members of the community is to remove all id games from portage. If |
40 |
there is someone else I should talk to about this, let me know so I can |
41 |
contact them. We appear to be at an impass since neither of us appears |
42 |
to be getting through to the other. |
43 |
|
44 |
> In the long run I'd like to have loki_setup use data files like win32 does |
45 |
> .msi files, that is having the installer engine compiled on the target |
46 |
> machine, and processing a data-only thing. That would probably keep us |
47 |
> safer from those endless ABI and app compability issues. I don't see when |
48 |
> I would have time to do that though. |
49 |
|
50 |
This would be quite cool, but would not solve any of the issues that are |
51 |
at hand. |
52 |
|
53 |
If there were a way to "force" the gtk installer to install the binaries |
54 |
and installations into certain directories, via the -b and -i options |
55 |
which are available to the command-line version, then there would be no |
56 |
issue here. I could use the loki_setup installer, have it display the |
57 |
EULA, and install where *I* tell it to via the ebuild. |
58 |
|
59 |
To be honest, I simply don't see how if I were to change the ebuild to |
60 |
display the EULA and force the user to accept before continuing does not |
61 |
meet the licensing requirements. Since I have repeated this and gotten |
62 |
no real response on it specifically other than you repeating about a |
63 |
wrapper, I am assuming that this is not acceptable to meet the license. |
64 |
|
65 |
I thank you for your time and for your great work in keeping gaming |
66 |
alive on Linux. |
67 |
|
68 |
Good day. |
69 |
|
70 |
Chris Gianelloni |
71 |
|
72 |
> regards |
73 |
> |
74 |
> TTimo |
75 |
> |
76 |
> On 19 Sep 2003 09:54:46 -0400 |
77 |
> Chris Gianelloni <wolf31o2@g.o> wrote: |
78 |
> |
79 |
> > On Fri, 2003-09-19 at 09:27, Timothee Besset wrote: |
80 |
> > > You DO modify the installer, otherwise there would be no question of |
81 |
> > > EULA display or not. The EULA has to be displayed if the original .run |
82 |
> > > is executed as is. Yes, it means ET has to be installed interactively |
83 |
> > > with an actual agreement of the end user, that what the lawyers want .. |
84 |
> > |
85 |
> > Once again, the .run file has the same md5sum as one downloaded from a |
86 |
> > normal mirror. The ebuild downloads the files from the same mirrors a |
87 |
> > user would. My dilemma comes in the fact that all applications in |
88 |
> > Gentoo need to have a non-interactive installation. I *can* break that |
89 |
> > by REQUIRING a user agree to a displayed EULA before installtion |
90 |
> > continues, but I cannot allow the ebuild to simply run the .run simply |
91 |
> > because our package management system would have zero knowledge of the |
92 |
> > files installed by ET on the live file-system. This is not acceptable. |
93 |
> > I have proposed a method where a EULA is displayed before installation |
94 |
> > continues. |
95 |
> > |
96 |
> > The Gentoo ebuild does not modify a single file in the Enemy Territory |
97 |
> > distribution. It simply unpacks the Makeself binary into a temporary |
98 |
> > directory, then copies files to the destination sandbox before putting |
99 |
> > moving the files onto the live file-system. Everything is simply a |
100 |
> > copy. The only "modification" done at all is a final chmod games.games |
101 |
> > on all of the files once installation is completed. |
102 |
> > |
103 |
> > This would all be solved if the loki_setup -n would not Segmentation |
104 |
> > Fault when run. I have no problems using the loki_setup if it would |
105 |
> > work properly with -n -b and -i, but it does not. |
106 |
> > |
107 |
> > Is making the user agree to the EULA sufficient? |
108 |
> > |
109 |
> > If not, then I will be forced to remove all id software from Gentoo due |
110 |
> > to licensing problems. Please advise me as quickly as possible so I can |
111 |
> > work to make Gentoo compliant as quickly as possible. |
112 |
> > |
113 |
> > > The situation is unchanged really, I think you should put the .run on |
114 |
> > > the system, with a fake 'et' script, which will spawn the .run the first |
115 |
> > > time it is executed interactively. |
116 |
> > |
117 |
> > We DO put the .run on the system. However, we simply execute it via |
118 |
> > portage, so there are sufficient rights to install the game for all |
119 |
> > users to use and also so the files installed by the game are tracked via |
120 |
> > our package management system for easy removal or upgrade. The |
121 |
> > setup.gtk binary is not sufficient for portage to track the files. The |
122 |
> > setup binary (with -b and -i) would be, but it seems to segfault when |
123 |
> > attempted. |
124 |
> > |
125 |
> > For this reason, if a compromise cannot be reached, I will remove all id |
126 |
> > games from portage, simply because there is zero reason to have them in |
127 |
> > portage at all if portage cannot track their versions and files |
128 |
> > properly. It would then be up to the user to download and install the |
129 |
> > game normally. |
130 |
> > |
131 |
> > At this time, it appears that there are 12 ebuilds which would need to |
132 |
> > be removed. This includes Return to Castle Wolfenstein, Quake 3 Arena |
133 |
> > (and all of its mods, since the dependency tree would be broken |
134 |
> > otherwise), and Enemy Territory. |
135 |
> > |
136 |
> > Let me know what I should do. |
137 |
> > |
138 |
> > > regards |
139 |
> > > |
140 |
> > > TTimo |
141 |
> > > |
142 |
> > > Chris Gianelloni wrote: |
143 |
> > > |
144 |
> > > >I am resending this since I got no response from the first one sent |
145 |
> > > >Monday. I would love to get this resolved as soon as possible. |
146 |
> > > > |
147 |
> > > >On Mon, 2003-09-15 at 09:12, Timothee Besset wrote: |
148 |
> > > > |
149 |
> > > > |
150 |
> > > >>There are two main requirements with everything we release: |
151 |
> > > >> |
152 |
> > > >>- Unmodified installer, the files should be distributed the same as we |
153 |
> > > >>release them, specially regarding the End User License Agreement prompt. |
154 |
> > > >> |
155 |
> > > >> |
156 |
> > > > |
157 |
> > > >We do not modify the installer. Would us adding a display of the EULA |
158 |
> > > >and forcing the user to agree before unpacking/installing suffice? If |
159 |
> > > >not, I can rewrite the ebuild to possibly make use of loki_setup doing |
160 |
> > > >most of the work unattended. The problem lies in the variable ways in |
161 |
> > > >which Gentoo installs. All installations take place in a sandbox and |
162 |
> > > >are only moved to the live filesystem once the install process has |
163 |
> > > >completed with no errors. Otherwise, there is no way for portage to |
164 |
> > > >track the files that are changed on the local disk without considerable |
165 |
> > > >cost in developer time. |
166 |
> > > > |
167 |
> > > > |
168 |
> > > > |
169 |
> > > >>- Only electronic redistributions. Which means files should never be |
170 |
> > > >>printed on CD without explicit permission from us. |
171 |
> > > >> |
172 |
> > > >> |
173 |
> > > > |
174 |
> > > >Gentoo Games is commercial entity independent of the distribution and |
175 |
> > > >the distribution's Games Team. The Games Team of the distribution will |
176 |
> > > >work with you to quickly resolve this problem. Any correspondence about |
177 |
> > > >Gentoo Games should be directed to Daniel Robbins |
178 |
> > > >(drobbins@g.o). I know that all releases from Gentoo Games are |
179 |
> > > >done electronically at this time. |
180 |
> > > > |
181 |
> > > > |
182 |
> > > > |
183 |
> > > >>We use loki_setup installer because we are not distribution centric. Doing |
184 |
> > > >>a .deb .rpm .whatever for each release would be a pain, and we don't want |
185 |
> > > >>to do that. And we don't want others doing it for us because we would |
186 |
> > > >>still get bug reports about those modified installers, and still waste |
187 |
> > > >>some time. |
188 |
> > > >> |
189 |
> > > >>loki_setup has many issues, I can't say I'm really happy with it. But we |
190 |
> > > >>will stick to it. The main issues with it seem to be ABI brokeness in |
191 |
> > > >>newer distributions, and misc issues like the 'head' thing. If you really |
192 |
> > > >>want to have an ebuild with ET, what I'd suggest doing is wrap the |
193 |
> > > >>download of the .run, and execute it for installation. |
194 |
> > > >> |
195 |
> > > >> |
196 |
> > > > |
197 |
> > > >If my suggestion above will not suffice, this may be our only option |
198 |
> > > >aside from removing id games altogether. |
199 |
> > > > |
200 |
> > > >I will also be forwarding this (and all future) correspondence to the |
201 |
> > > >gentoo-core private mailing list for the Gentoo developers. I will pass |
202 |
> > > >any questions the other developers may have on to you. |
203 |
> > > > |
204 |
> > > > |
205 |
> > > > |
206 |
> > > >>regards |
207 |
> > > >> |
208 |
> > > >>TTimo |
209 |
> > > >> |
210 |
> > > >>On 14 Sep 2003 14:51:37 -0400 |
211 |
> > > >>Chris Gianelloni <wolf31o2@g.o> wrote: |
212 |
> > > >> |
213 |
> > > >> |
214 |
> > > >> |
215 |
> > > >>>I was just made aware of the issue with Enemy Territory and the EULA as |
216 |
> > > >>>it concerns Gentoo. As the maintainer of this package, I would like to |
217 |
> > > >>>work with you on a resolution. At this time, I have blocked the package |
218 |
> > > >>>from installing in portage until a resolution can be made. Get back to |
219 |
> > > >>>me as soon as you get a chance so we can resolve this quickly. |
220 |
> > > >>> |
221 |
> > > >>>Thanks, |
222 |
> > > >>> |
223 |
> > > >>>-- |
224 |
> > > >>>Chris Gianelloni |
225 |
> > > >>>Developer, Gentoo Linux |
226 |
> > > >>>Games Team |
227 |
> > > >>> |
228 |
> > > >>>Is your power animal a penguin? |
229 |
> > > >>> |
230 |
> > > >>> |
231 |
> > > >>> |
232 |
> > -- |
233 |
> > Chris Gianelloni |
234 |
> > Developer, Gentoo Linux |
235 |
> > Games Team |
236 |
> > |
237 |
> > Is your power animal a pengiun? |
238 |
> > |
239 |
-- |
240 |
Chris Gianelloni |
241 |
Developer, Gentoo Linux |
242 |
Games Team |
243 |
|
244 |
Is your power animal a pengiun? |