Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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: <4.3.1.2.20020416111642.057cab80@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
Date: Tue, 16 Apr 2002 11:32:16 -0400
To: <fergus AT bonhard DOT uklinux DOT net>, <cygwin AT cygwin DOT com>
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: New 'release' directory - was Re: Reversion to earlier
  behaviour 
In-Reply-To: <000701c1e523$98bb1ca0$6fc82486@medschool.dundee.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 04:49 AM 4/16/2002, fergus AT bonhard DOT uklinux DOT net wrote:
>Strange (but nice). Every so often I do a clean install from scratch. I did
>it today when the installation directories contrib/ + latest/ became
>release/. 


Yep.  That's the result of directory reorganization that was discussed on 
the cygwin-apps list just yesterday.  Check the email list archives if you're
interested in the details.


>Ages ago all customisations incl. aliases etc were read from my
>~/.bash_profile. Then the bash version changed and I had to export SHELL=,
>and define all aliases, in ~/.bashrc. After today's new installation I find
>things are back to the former architecture: everything picked up from
>~/.bash_profile. Strange (nothing significant in the provision seems to have
>altered since yesterday). Nice (simple, elegant). But correct? expected?


I'm not sure why the behavior would've changed for you, all other things 
being equal.  The bash man page clearly states that `/.bash_profile, along
with other script files, will be automatically executed for any login shell.
If this is how things work for you now and your method of invoking bash has
not changed, then the previous behavior you were seeing was wrong.  I can't
say whether this problem was due to some problem in your environment 
(probably) or some bug that your installation tickled (possible).

As for exporting 'SHELL', this has been discussed ad-nauseam on this list.
I guess if you're really interested in understanding this change, you'll 
review the bash announcements from Chet Ramey.  He clearly enumerated the 
changes in the last bash release with respect to the list of exported 
variables.


Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/