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
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Tue, 11 Jul 2000 22:08:45 -0400
To: cygwin-developers AT sourceware DOT cygnus DOT com
Subject: Re: new setup.exe in cvs!
Message-ID: <20000711220845.B31687@cygnus.com>
Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com
Mail-Followup-To: cygwin-developers AT sourceware DOT cygnus DOT com
References: <200007070103 DOT VAA07398 AT envy DOT delorie DOT com> <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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <200007112102.RAA03615@envy.delorie.com>; from dj@delorie.com on Tue, Jul 11, 2000 at 05:02:33PM -0400

On Tue, Jul 11, 2000 at 05:02:33PM -0400, DJ Delorie wrote:
>> A possible solution could be to implement a tar file with something
>> like a 'postinstall.sh' in it and the general files in it. this
>> package could install to /tmp, setup calls it after the mount points &
>> everything is set up and running and all the maintainance with
>> removing files, renaming config etc. could be done there.
>
>If/when RPM support is integrated into setup, we can do this.  Until
>then, I think sticking with what setup does now is best for what FAQs
>I've seen on the mailing list so far.

I like the postinstall.sh idea, actually.

There have been requests that we do things after setup has completed
installing packages.  I started to implement something like this in the
previous version, except I was going to use a .bat file.

I didn't use /bin/sh because it is theoretically possible that the
user could not have /bin/sh installed on their system.

Things that we could do are:

mkdir -p /tmp /var/run /usr/local/lib /usr/local/bin /usr/local/include
touch /var/run/utmp
mkgroup
mkpasswd
create /usr/info/dir
remove empty /usr/i686-pc-cygwin/... tree

There are probably many more things that could be done and the nice
thing about putting this in a script is that we wouldn't have to
recompile setup.exe to accomplish this.

cgf