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 sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Message-ID: <20000427115224.23215.qmail@web124.yahoomail.com> Date: Thu, 27 Apr 2000 04:52:24 -0700 (PDT) From: Earnie Boyd Reply-To: earnie_boyd AT yahoo DOT com Subject: Re: setup issues To: DJ Delorie , cygwin-developers AT sourceware DOT cygnus DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- DJ Delorie wrote: > > That won't work if we store multiple versions, which I think we should > allow for. Better, a separate subdir of symbolic links of "everything > you need", that setup either uses or knows to ignore. > I like this option. The symbolic link then would need to be updated with the most current stable version. > > Then, when someone has a problem we just have to tell them to download > > setup.exe and all of the above files and then run setup. > > The behemoth setup.exe (full.exe?) is a better idea. We just have to > automate building it (a setup.exe option? ;) Maybe. I've real mixed feelings on this. Hmm... full.exe could be a "self-extracting" zip file. Then the use would execute full followed by an execution of setup. Uhm, rather than full.exe how about user-tools and dev-tools. I've always thought that the full, and user-tools was confusing. With user-tools and dev-tools you'ld have to get both to have the whole shebang. Cheers, ===== --- Earnie Boyd: __Cygwin: POSIX on Windows__ Cygwin Newbies: __Minimalist GNU for Windows__ Mingw32 List: Mingw Home: __________________________________________________ Do You Yahoo!? Talk to your friends online and get email alerts with Yahoo! Messenger. http://im.yahoo.com/