From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stipe Tolj To: earnie_boyd@yahoo.com Cc: "Smith, Martin" , Cygwin Subject: Re: [ANN] Cygwin DEV survey Date: Tue, 09 Mar 1999 17:40:00 -0000 Message-id: <36E5C95D.7810@uni-duesseldorf.de> References: <19990308134915.8672.rocketmail@send101.yahoomail.com> X-SW-Source: 1999-03/msg00309.html Earnie Boyd wrote: > > * Of course, using InstallShield, you could offer some of these as > > options under "Custom" setup. > 8< > > Yuk. Just give me a tarball please. the cygwin port packages will be available as tarballs for after-install use, but the basic installation procedure for core cygwin and all pre-compiled packages will be within InstallShield since it is a very powerfull tool for such purposes on Win32 systems and new cygwin users should be more familiar with InstallShield than saying "tar xfz foo.tar.gz" within a non-DOS bash shell. > I like the idea, too. However, it is a given that you'll never > satisfy everyone and if you're too lazy to read do the FAQ session > then you're going to be too lazy to read any other installation manual > as well. I can just hear the questions now, "I just got this CD and > I'm trying to ...". ;^) Hmmm, that's why we want to build the CD environment as clean as possible, like SuSE does it with the latest 6.0 release. Mainly all packages should work after installation. Support for re-compiling the packages will be very limited. Regards, Stipe -- Stipe Tolj Cygwin Porting Project Department of Economical Computer Science University of Cologne, Germany http://www-public.rz.uni-duesseldorf.de/~tolj -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stipe Tolj To: earnie_boyd@yahoo.com Cc: "Smith, Martin" , Cygwin Subject: Re: [ANN] Cygwin DEV survey Date: Wed, 31 Mar 1999 19:45:00 -0000 Message-ID: <36E5C95D.7810@uni-duesseldorf.de> References: <19990308134915.8672.rocketmail@send101.yahoomail.com> X-SW-Source: 1999-03n/msg00309.html Message-ID: <19990331194500._b_NqvIif5C332r9mLJmOTD-Q2LzRKVOJ_iPXus-Iuk@z> Earnie Boyd wrote: > > * Of course, using InstallShield, you could offer some of these as > > options under "Custom" setup. > 8< > > Yuk. Just give me a tarball please. the cygwin port packages will be available as tarballs for after-install use, but the basic installation procedure for core cygwin and all pre-compiled packages will be within InstallShield since it is a very powerfull tool for such purposes on Win32 systems and new cygwin users should be more familiar with InstallShield than saying "tar xfz foo.tar.gz" within a non-DOS bash shell. > I like the idea, too. However, it is a given that you'll never > satisfy everyone and if you're too lazy to read do the FAQ session > then you're going to be too lazy to read any other installation manual > as well. I can just hear the questions now, "I just got this CD and > I'm trying to ...". ;^) Hmmm, that's why we want to build the CD environment as clean as possible, like SuSE does it with the latest 6.0 release. Mainly all packages should work after installation. Support for re-compiling the packages will be very limited. Regards, Stipe -- Stipe Tolj Cygwin Porting Project Department of Economical Computer Science University of Cologne, Germany http://www-public.rz.uni-duesseldorf.de/~tolj -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com