Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <03F4742D8225D21191EF00805FE62B9908E23EDD@aa-msg-01.medstat.com>
From: John Wiersba <John DOT Wiersba AT medstat DOT com>
To: cygwin AT cygwin DOT com
Subject: RE: "shouted down", "shot down", apologies
Date: Wed, 27 Jun 2001 18:44:18 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 27 Jun 2001 22:44:08.0847 (UTC) FILETIME=[AD7269F0:01C0FF5A]

> -----Original Message-----
> From: Greg Smith [mailto:gsmith AT nc DOT rr DOT com]
> Sent: Wednesday, June 27, 2001 6:35 PM
> To: cygwin AT cygwin DOT com
> Subject: Re: "shouted down", "shot down", apologies
> 
> 
> John Wiersba wrote:
>
> > Back to my original question (building entire cygwin suite 
> > from source):
> 
> Umm, what we're talking here is not building the packages 
> that are provided
> with Cygwin, but rather the support programs that enable 
> Cygwin to do its thing.
> For example, cygwin1.dll
> 
> To compile/build the other stuff, you'll need to download the 
> package sources and
> follow the build instructions for each package.

Well, what I'd like to do, and what should be standard for any package
accepted into the cygwin archive (available to be downloaded with
setup.exe), is that each package source tarball should build out-of-the-box
under cygwin with a simple make configure; make; make test (check?); make
install, including the most recent "stable" cygwin source tarball.  With a
little extra work (getting them to install to a directory hierarchy not
rooted at /) I should be able to rebuild each of the binary tarballs
downloadable with setup.exe.

If I want to build the bleeding edge cygwin package, I'll have to use cvs to
get it.  But right now, all I want to do is rebuild the "stable" packages.

-- John Wiersba

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/