Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Message-ID: <001f01c1fe1c$ecd4e840$c23fa8c0@transarc.ibm.com>
From: "Michael Young" <mwy-ltua@the-youngs.org>
To: "Robert Collins" <robert.collins@itdomain.com.au>, <cygwin@cygwin.com>
References: <FC169E059D1A0442A04C40F86D9BA7600C6104@itdomain003.itdomain.net.au>
Subject: Re: PGP signatures for packages?
Date: Fri, 17 May 2002 23:34:32 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200

> And adding GPG as a package should be easy. There is already vounteer
> binary downloads 'out there'. You just need to merge tehir build recipe
> and patchs and the volunteer maintainer instructions.

My understanding is that the official Windows binaries for GnuPG are
built on Linux using a cross-compiler.  I don't suppose that's a
legitimate approach for an official Cygwin package, though, is it?
I'll look at what it will take to do a native configure/compile.



--
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/

