From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28740 invoked by alias); 9 Nov 2008 06:18:24 -0000 Received: (qmail 28698 invoked by uid 22791); 9 Nov 2008 06:18:23 -0000 X-Spam-Check-By: sourceware.org Received: from hs-out-0708.google.com (HELO hs-out-0708.google.com) (64.233.178.249) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 09 Nov 2008 06:17:25 +0000 Received: by hs-out-0708.google.com with SMTP id k27so906812hsc.2 for ; Sat, 08 Nov 2008 22:17:23 -0800 (PST) Received: by 10.65.123.10 with SMTP id a10mr5619431qbn.79.1226211443017; Sat, 08 Nov 2008 22:17:23 -0800 (PST) Received: from ?192.168.0.100? (S0106001346f94b85.wp.shawcable.net [24.76.249.6]) by mx.google.com with ESMTPS id s31sm5772446qbs.8.2008.11.08.22.17.21 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 08 Nov 2008 22:17:22 -0800 (PST) Message-ID: <49168071.3050405@users.sourceforge.net> Date: Sun, 09 Nov 2008 06:18:00 -0000 From: "Yaakov (Cygwin Ports)" User-Agent: Thunderbird 2.0.0.17 (Windows/20080914) MIME-Version: 1.0 To: cygwin-apps@cygwin.com Subject: Re: cygport-0.9.3 in release-2 References: <4906B2F8.4000708@users.sourceforge.net> <747eg4dsfpl4befpo8gb4qkgo3sm0d8fbi@4ax.com> <747eg4dsfpl4befpo8gb4qkgo3sm0d8fbi-e09XROE/p8c@public.gmane.org> <4907C0F1.2040005@cwilson.fastmail.fm> <4914ED2E.3000106@cwilson.fastmail.fm> In-Reply-To: <4914ED2E.3000106@cwilson.fastmail.fm> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2008-11/txt/msg00059.txt.bz2 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Charles Wilson wrote: > Okay, so these are (mostly) your own custom patches needed to port the > code to cygwin, and not "official" patches from somewhere else, like > > 1) bugfixes taken wholesale from another distro > (http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-libs/ncurses/files/) > 2) intra-release patches (see ftp://invisible-island.net/ncurses/5.6/) > > If it were 1) or 2), I'd suggest using > > PATCH_URI="http://sources.gentoo.org/viewcvs.py/gentoo-x86/sys-libs/ncurses/files/ncurses-5.6-build.patch > > ftp://invisible-island.net/ncurses/5.6/ncurses-5.6-coverity.patch.gz" BTW, that's mirror://portage/sys-libs/ncurses/... for short, but you've got the idea. > a) my example, ncurses, has a LOT (50 or so) "official" patches > b) they are all gz-compressed; cygport might not support compressed > patches in PATCH_URI Compressed single patches are supported in PATCH_URI since 0.3.5. > So, in fact, for ncurses (where some of the official upstream "patches" > are actually shell scripts with shar-compressed patches!) I actually > DON'T specify these files in PATCH_URI. Instead, I specify them in > SRC_URI, and then use src_unpack_hook to apply (that is, execute!) them. Interesting, I'd like to see those "patches"; with the recent release of ncurses-5.7, all the 5.6 patches are gone. > Yaakov? Pretty please? I think you know that I haven't been a big fan of this idea. Nevertheless, cygport 0.9.x allows you to call src_compile(), src_install(), or any self-defined function on the command line, but it doesn't allow for any arguments to the function. Adding that limitation made the implementation much easier than what you were proposing, and I hope that it will be sufficient. Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAkkWgHAACgkQpiWmPGlmQSMO6wCZAYYFbbjEz7ufFJ5fkdJHXslc 3c4AoOCOv5aK+iO/Q2+3Z0g0p+f+A5vV =/NPh -----END PGP SIGNATURE-----