Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <42667BBA.50F9C6E0@dessent.net>
Date: Wed, 20 Apr 2005 08:56:42 -0700
From: Brian Dessent <brian AT dessent DOT net>
Organization: My own little world...
MIME-Version: 1.0
To: Cygwin List <cygwin AT cygwin DOT com>
Subject: Re: How well supported is csh/tcsh?
References: <42667561 DOT 5040305 AT ieee DOT org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com

Jason Pearce wrote:

> o Do most new/upgraded packages work or do you always have to port setup
> scripts?

In this case it shouldn't matter.  All postinstall / preremove scripts
are intended to be run by (and are in fact run by) /bin/sh, aka ash,
regardless of what shell you choose as a user.  Now if you're saying
that you're going to remove ash then yes, expect a whole buttload of
stuff to break.  But if you just switch to tcsh as your default shell
but leave ash sitting around as /bin/sh, then everything should be
fine.  The same thing goes for scripts used by packages (for example
ssh-host-config) because they all reference /bin/sh or /bin/bash in the
shebang, and so as long as you don't do something silly like remove ash
or bash then you're fine.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/