From: Justin Whitney <ripple.gentoo@ripple.be>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] initscripts in python
Date: 15 Apr 2003 21:29:10 -0400 [thread overview]
Message-ID: <1050456550.2602.24.camel@osiris.ripple.be> (raw)
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
next reply other threads:[~2003-04-16 1:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 1:29 Justin Whitney [this message]
2003-04-16 4:09 ` [gentoo-dev] initscripts in python 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
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=1050456550.2602.24.camel@osiris.ripple.be \
--to=ripple.gentoo@ripple.be \
--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