public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sven Vermeulen <swift@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] initscripts in python
Date: Wed, 16 Apr 2003 10:52:48 +0200	[thread overview]
Message-ID: <20030416085248.GD1795@Daikan.pandora.be> (raw)
In-Reply-To: <200304161019.31869.gentoo-user@devrieze.net>

[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]

On Wed, Apr 16, 2003 at 10:19:31AM +0200, Paul de Vrieze wrote:
> As most init scripts are essentially nobrainer oneliners, I believe using 
> anything but sh is overkill. In the cases where something special is required 
> it is very well possible to use python/any other language either embedded or 
> instead of the standard interpreter. (You could even make init scripts in c)

I agree. The cons for using Python-based initscripts are too important. 

First of all it's important that the system still boots, even when Python
doesn't work due to a bad ebuild or any other circumstance. Saying that this
is the same for when the shell itself doesn't work isn't true, since you'll
need the shell in order to fix the problem. You don't need Python.

Second is that there are lots of users that can shellscript (it's not that
difficult) but who don't know how to code in Python. They'll seriously object
when Gentoo would start using Python initscripts.

This would also mean that Python should be moved from /usr/lib to /lib,
increasing the size of the / partition and removing the possibility for
shared Python in a network (admin POV).

I also think that the initialisation time would increase, leaving us with no
real advantage whatsoever. 

If you want speed, just code them in C and compile :)

	Sven Vermeulen

-- 
	Fighting for peace is like fucking for virginity.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-04-16  8:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-16  1:29 [gentoo-dev] initscripts in python Justin Whitney
2003-04-16  4:09 ` Daniel Armyr
2003-04-16  5:38 ` merv
2003-04-16  7:25   ` Jeff Rose
2003-04-16  8:49     ` merv
2003-04-16  8:19   ` Paul de Vrieze
2003-04-16  8:52     ` Sven Vermeulen [this message]
2003-04-16 20:54       ` Justin Whitney
2003-04-17 20:05         ` merv
2003-04-17  5:49     ` Joseph Carter
2003-04-17  6:27       ` George Shapovalov
2003-04-17 18:25         ` merv
2003-04-17  7:42       ` Paul de Vrieze
2003-04-16 22:44   ` Abhishek Amit
2003-04-17  6:45     ` Sven Vermeulen
2003-04-17 20:56       ` merv
2003-04-17 22:26         ` Caleb Shay
2003-04-17 23:32           ` merv
2003-04-17 18:18     ` merv
2003-04-16 21:08 ` Brad Laue
2003-04-17  6:47   ` Sven Vermeulen
  -- strict thread matches above, loose matches on Subject: below --
2003-04-16 11:13 merv

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030416085248.GD1795@Daikan.pandora.be \
    --to=swift@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox