Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Tue, 11 Jul 2000 17:02:33 -0400 Message-Id: <200007112102.RAA03615@envy.delorie.com> From: DJ Delorie To: michael-ring AT t-online DOT de CC: cygwin-developers AT sourceware DOT cygnus DOT com In-reply-to: <0rumms8bd6f5g2aip0hh75hhe2vki9o84l@4ax.com> (michael-ring AT t-online DOT de) Subject: Re: new setup.exe in cvs! References: <200007070103 DOT VAA07398 AT envy DOT delorie DOT com> <200007101915 DOT PAA13577 AT envy DOT delorie 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> > But how far are you willing to go ? I think it is a nightmare to have > 'business logic' implemented into an installation program. > > 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.