[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] Re: <bug> shell scripts fail when /bin/sh <> /bin/bas

From: Karsten Hilbert
Subject: Re: [Gnumed-devel] Re: <bug> shell scripts fail when /bin/sh <> /bin/bash
Date: Sun, 3 Aug 2008 21:30:38 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

On Sun, Aug 03, 2008 at 08:27:46AM +0200, Gour wrote:

> True. I was thinking in the sense of pre-requirement: "In order to use
> GNUmed you have to run Posix-compliant shell!"
Well, *that* isn't true and IMO would be a rather shameful
requirement. Windows doesn't even *have* a POSIX compliant
shell (not sure about cygwin). I am not sure about the
MacOSX shell.

It is only a few helper shell scripts which have bashisms in
them which I would rather either fix or explicitely make
them require bash (as they do now).

> Karsten> Python isn't really the right tool for the job. Perhaps for
> Karsten> some but surely not for all things we use shell scripts for.
> I understand that it isn't being higher-level language.
> However, rewriting shell scripts in Python would eliminate problem of
> 'shell-compatibility'.
Most of those shell scripts are platform specific anyways.
That's why they are shell scripts in the first place - they
automate steps one would do on the command line.

> So, if you don't mind I can try write some Python code and replace shell
> scripts

Sure, why not. Which one are you thinking about ? It'll make
a lot more sense for some than for others.

Some of the shell scripts we'll keep in any case, however,
such as or /usr/bin/gnumed, because they
serve quite specific purposes for which the shell is the
appropriate level of abstraction.

GPG key ID E4071346 @
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346

reply via email to

[Prev in Thread] Current Thread [Next in Thread]