1 |
On Wed, Apr 16, 2003 at 10:19:31AM +0200, Paul de Vrieze wrote: |
2 |
> As most init scripts are essentially nobrainer oneliners, I believe using |
3 |
> anything but sh is overkill. In the cases where something special is required |
4 |
> it is very well possible to use python/any other language either embedded or |
5 |
> instead of the standard interpreter. (You could even make init scripts in c) |
6 |
|
7 |
I agree. The cons for using Python-based initscripts are too important. |
8 |
|
9 |
First of all it's important that the system still boots, even when Python |
10 |
doesn't work due to a bad ebuild or any other circumstance. Saying that this |
11 |
is the same for when the shell itself doesn't work isn't true, since you'll |
12 |
need the shell in order to fix the problem. You don't need Python. |
13 |
|
14 |
Second is that there are lots of users that can shellscript (it's not that |
15 |
difficult) but who don't know how to code in Python. They'll seriously object |
16 |
when Gentoo would start using Python initscripts. |
17 |
|
18 |
This would also mean that Python should be moved from /usr/lib to /lib, |
19 |
increasing the size of the / partition and removing the possibility for |
20 |
shared Python in a network (admin POV). |
21 |
|
22 |
I also think that the initialisation time would increase, leaving us with no |
23 |
real advantage whatsoever. |
24 |
|
25 |
If you want speed, just code them in C and compile :) |
26 |
|
27 |
Sven Vermeulen |
28 |
|
29 |
-- |
30 |
Fighting for peace is like fucking for virginity. |