1 |
Thanks for the arguments thus far. |
2 |
|
3 |
So added to the cons list is: |
4 |
|
5 |
*addition of newer less-tested interpreter could add instability |
6 |
*very small/short scripts incur overhead |
7 |
|
8 |
Here are two mitigating arguments to counter the first statement. |
9 |
|
10 |
First - a separate, stable build of python could be used as the |
11 |
system-boot interpreter. it might make sense to statically link it and |
12 |
so forth to lower dependencies... perhaps even to optimize it in some |
13 |
respects, for its task. |
14 |
|
15 |
Second, a shell script like the runscript.sh that is already used could |
16 |
be used to launch the interpreter and check for a runtime failure. On |
17 |
failure it could launch the .sh version of the bootscript. This means |
18 |
keeping two copies of the shellscripts obviously (which wouldn't be a |
19 |
bad idea anyway...) this would at least have the benefit of salvaging |
20 |
the boot... |
21 |
|
22 |
As for the overhead problem with very small scripts, I don't see that |
23 |
going away... in fact converting such scripts would be a waste of time |
24 |
in the first place, because it doesn't make use of any of the advantages |
25 |
proposed by the change. It would make more sense to set up the boot |
26 |
process to be able to run both kinds so you don't waste your time. |
27 |
|
28 |
--Justin |
29 |
|
30 |
|
31 |
-- |
32 |
gentoo-dev@g.o mailing list |