Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Message-ID: <20000126162956.4192.qmail@web111.yahoomail.com>
Date: Wed, 26 Jan 2000 08:29:56 -0800 (PST)
From: Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To: earnie_boyd AT yahoo DOT com
Subject: Re: next net release preliminary info
To: DJ Delorie <dj AT delorie DOT com>, cygwin-developers AT sourceware DOT cygnus DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

--- DJ Delorie <dj AT delorie DOT com> wrote:
> 
> OK, it's my turn to do a cygwin net release, and I've talked Chris
> into letting me try doing it a different way (hopefully this will
> benefit the net community in the long run).  So, here's my ideas.
> 
> First, we'll split up the release into separate tarballs for each
> package (cygwin, gcc, gdb, etc).  That way, (1) users can download
> just what they want, and (2) we can update individual packages as
> they're released instead of waiting forever to release everything all
> at once.
> 

I like this much.

> Second, each "package" gets its own directory.  Thus, there will be a
> top-level "make" directory that contains the latest binaries, sources,
> patches, old versions if needed, etc.  ftp.gnu.org does this, and it
> makes for a much cleaner top-level directory.
> 

This is good too.  I would like to see the things common to each package,
things like readline, intl, etc. moved to this level and removed from the
package for the sake of the cygwin distributions as well.  This would cut down
on the size of each package but would require managing dependencies
differently.

> We're still trying to figure out what to do about a setup/install
> program.  I've got dreams of an "ideal" program, but it would take too
> long to do.  I've cobbled together a zip of the minimum startup files
> (tar and gzip) for now.
> 
> If anyone has any comments, opinions, or requests, now's the time to
> post them.
> 

I've added a quote from the Mingw32 list about "Freeware" installers.  Haven't
checked them myself.

Earnie.

------Quote from the Mingw32 list follows-------
"alfred reibenschuh" alfred DOT reibensch- AT chello DOT at wrote: 
original article:http://www.egroups.com/group/mingw32/?start=1110
> check this out:
> 
> http://netnet.net/~freeman/

In case you're interested, here are some other links to freeware
install programs for Windows (or DOS).

http://www.ddj.com/ftp/1995/1995.09/install.zip
-Source code from an article on how to write an installer
http://www.freebyte.com/ - HJ-Install
http://www.jordanr.dhs.org - Inno Setup
ftp://x2ftp.oulu.fi/pub/msdos/programming/utils/inst101.zip - DOS
program

This is definitely one area that's missing in compiler distributions if
you don't purchase MSVC, Borland or a compiler that comes with a
professional install package.

Anyone have URLs for ported Linux/Unix install programs they want to
mention?

Laura Michaels
http://members.aol.com/lauram3017/index.html

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com