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
Message-ID: <08a601c1722e$9ee6ea40$0200a8c0@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Paul Garceau" <pgarceau AT qwest DOT net>, <cygwin-apps AT cygwin DOT com>
References: <OE45lk5wQlqlTPX4R0P00013cf7 AT hotmail DOT com> <3BFA890F DOT 18658 DOT E5AD8D AT localhost>
Subject: Re: -src package standard: proposal #5 and #5a
Date: Wed, 21 Nov 2001 12:48:29 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-OriginalArrivalTime: 21 Nov 2001 01:48:25.0518 (UTC) FILETIME=[9C0C04E0:01C1722E]

----- Original Message -----
From: "Paul G." <pgarceau AT qwest DOT net>

> Now, to the issue at hand:
>
> Complete Source?
>
> Finally, for those who don't care about dependencies, and typically
> download "All" the source, there is added a new category
defined/called
> "Cygwin -- Complete Source" (for lack of a better description).

This is a good point, one I hadn't considered. Added to the wishlist.

However:
IMO setup.exe as a installer/bootstrapper should not manage source code
trees
- download yes
- install/build/update no.

I think I've been consistent about this :}. I think that there should be
tools for the users to apply to the downloaded source, and that they
should be able to use setup.exe as a batch tool to grab source.

The rpm BuildReq and deb Build-depends tags are identical afaict - they
specify what _binary_ packages are needed to build a given source
package.

i.e. to build curl+ssl one needs (in a fully split up package world),
libcygwin-dev, libssl-dev. And they in turn depend on libcygwin and
libssl.

I like the concepts you've outlined, but I think it's much better to
leverage the existing batch style tools for either rpm or debs that
provide the same capabilities. Which means either convert those tools to
work with cygwin packages, or get setup to work with those tools :}.

Sigh.

Rob