Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Thu, 13 Jul 2000 16:58:09 -0400
Message-Id: <200007132058.QAA26680@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to: <20000712135224.B2568@cygnus.com> (message from Chris Faylor on
	Wed, 12 Jul 2000 13:52:24 -0400)
Subject: Re: new setup.exe in cvs!
References: <mv5kmsg0amn2tsvcl1oq0s8llhroghe9r4 AT 4ax DOT com> <200007101915 DOT PAA13577 AT envy DOT delorie DOT com> <at8kmskh6i9r1dkl0hgrv6hqjk22f1snfo AT 4ax DOT com> <200007111805 DOT OAA02322 AT envy DOT delorie DOT com> <12tmms0q9ff43hqdukairos23ga27421rl AT 4ax DOT com> <200007111938 DOT PAA02935 AT envy DOT delorie DOT com> <0rumms8bd6f5g2aip0hh75hhe2vki9o84l AT 4ax DOT com> <200007112102 DOT RAA03615 AT envy DOT delorie DOT com> <20000711220845 DOT B31687 AT cygnus DOT com> <200007121635 DOT MAA21003 AT envy DOT delorie DOT com> <20000712135224 DOT B2568 AT cygnus DOT com>


> On Wed, Jul 12, 2000 at 12:35:09PM -0400, DJ Delorie wrote:
> >I've checked in a patch to setup that moves the mkgroup/mkpasswd stuff
> >into /etc/postinstall/*.sh, and added support to /etc/profile to run -
> >once - any script found as /etc/postinstall/*.sh.  I also only do the
> >mkgroup/mkpasswd stuff if the install happens on NT.
> 
> I still don't understand why you'd put this burden on bash.  If things
> need to be setup shouldn't setup be doing the setup?

OK, this is where it's at now:

* Setup will look for /etc/passwd and /etc/group, and create its own
  postinstall/*.bat to create whatever's missing.

* setup will look for /etc/postinstall/*.sh, and run each with
  whatever shell it can find (sh, else bash), if any shell can be
  found at all.  These scripts are renamed to <script>.done once
  they've been run (so they won't run again, yet you can audit them).

* Same for /etc/postinstall/*.bat, with cmd.exe (NT) or command.com
  (others).

This is all done at the end of setup, so I took the extra code out of
/etc/profile.  I left in the /etc/profile.d/*.sh code, as some
packages may provide those for per-user configurations.