Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Date: Wed, 21 Nov 2001 21:36:13 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-apps AT cygwin DOT com
Subject: Remove cinstall src directory from snapshots
Message-ID: <20011122023613.GA8976@redhat.com>
Reply-To: cygwin-apps AT cygwin DOT com
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.23.1i

How should the sources for utils and cinstall be distributed?

I have just managed to separate winsup/utils as a separate binary
release but I'm not 100% certain how to release the sources.

winsup/utils is pretty useless without the cygwin directories, I think.
It can probably get by with the installed mingw/w32api, though.

So, I'm not sure how to release utils.  Maybe I need to separate out
the parts of cygwin that get used by utils and put it in a separate
directory.

Wrt to cinstall, I'd like to stop including the sources in snapshots and
net releases.  I believe that means that we'll have to release the sources
via some other method to be GPL compliant.

I know that Robert has a plan for this but maybe this is as simple as
just including a tar ball next to setup.exe at sources.redhat.com.

cgf