From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24430 invoked by uid 1002); 16 Apr 2003 04:13:13 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 30114 invoked from network); 16 Apr 2003 04:13:12 -0000 Message-ID: <3E9CD787.3000307@home.se> Date: Wed, 16 Apr 2003 12:09:43 +0800 From: Daniel Armyr User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030401 X-Accept-Language: en-us, en, sv MIME-Version: 1.0 To: gentoo-dev@gentoo.org References: <1050456550.2602.24.camel@osiris.ripple.be> In-Reply-To: <1050456550.2602.24.camel@osiris.ripple.be> X-Enigmail-Version: 0.71.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [gentoo-dev] initscripts in python X-Archives-Salt: b35b2a83-5ec0-41a6-85c1-7330507017c0 X-Archives-Hash: 4a782b5e85b960566453c2c30bf92aa7 I definately like the idea, especially since I am one of those who knows most programming-languages, but hasn't a clue about how to use all those wierd little mini-programs. However, I am afraid the cons you proposed are quite substantial and cannot be overlooked. //Daniel Armyr Justin Whitney wrote: >Hi, > >I don't really like talking about these kinds of vague ideas (like I'm >doing here), because that doesn't get them written - but this one I want >feedback on first before I dive in... so... > >For a lot of reasons I'd like to implement the initscrits in something >other than shell script. Something like python, say. > >Reasons for doing this would include: > >*writing (advanced) shellscripts requires learning awk/sed, and various >other minor tools (mostly because their features aren't supported by the >language). Use of a language with these features builtin lowers the >learning requirement, or at least puts it all under one roof. >*improved performance and bytecode-compilability >*Speedups due to fewer exec calls (for awk/sed/etc) > >Reasons NOT to do this would include: > >*breaking from standard would mean packages with provided initscripts >would require a rewrite. >*slight increase in boot requirements (interpreter and libs must exist >at least minimally on root partition) >*probably needs a bit more memory > >other bits: > >*compatibility could obviously be maintained, as existing shell scripts >could still be run without changes. > > >Note: I am by no means proposing this as a standard feature of gentoo. > >That said, since gentoo already uses python for portage, selecting >python as the language to use makes sense. Aside from the re-writes, >and some other details, I don't see much disadvantage to the above >design. > >Comments appreciated. > >--Justin Whitney > > >-- >gentoo-dev@gentoo.org mailing list > > > > > -- gentoo-dev@gentoo.org mailing list