From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22084 invoked by alias); 10 Nov 2008 15:38:55 -0000 Received: (qmail 22005 invoked by uid 22791); 10 Nov 2008 15:38:54 -0000 X-Spam-Check-By: sourceware.org Received: from qmta08.westchester.pa.mail.comcast.net (HELO QMTA08.westchester.pa.mail.comcast.net) (76.96.62.80) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 10 Nov 2008 15:38:06 +0000 Received: from OMTA02.westchester.pa.mail.comcast.net ([76.96.62.19]) by QMTA08.westchester.pa.mail.comcast.net with comcast id dQBF1a0070QuhwU58TdYz2; Mon, 10 Nov 2008 15:37:32 +0000 Received: from helium ([69.140.155.53]) by OMTA02.westchester.pa.mail.comcast.net with comcast id dTe31a00N19PpZx3NTe4Ym; Mon, 10 Nov 2008 15:38:04 +0000 X-Authority-Analysis: v=1.0 c=1 a=l2XSmzYQ2LBzthI_m0oA:9 a=RWkr5_3xsz5L_zQJmcJeVMbDtbIA:4 a=MxZ3bB5I4kYA:10 Received: from helium ([127.0.0.1] helo=D77E1BASCHULMA1.aa.ad.epa.gov) by helium with smtp (Exim 4.69) (envelope-from ) id 1KzYq3-0001b2-Jy for cygwin-apps@cygwin.com; Mon, 10 Nov 2008 10:38:03 -0500 From: Andrew Schulman To: cygwin-apps@cygwin.com Subject: Re: cygport-0.9.3 in release-2 Date: Mon, 10 Nov 2008 15:38:00 -0000 Message-ID: References: <4906B2F8.4000708@users.sourceforge.net> <747eg4dsfpl4befpo8gb4qkgo3sm0d8fbi@4ax.com> <747eg4dsfpl4befpo8gb4qkgo3sm0d8fbi-e09XROE/p8c@public.gmane.org> <4907C0F1.2040005@cwilson.fastmail.fm> <49167C17.9050106@users.sourceforge.net> In-Reply-To: <49167C17.9050106@users.sourceforge.net> X-Mailer: Forte Agent 4.2/32.1118 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Archive: encrypt 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/msg00068.txt.bz2 > > Several of my packages require multiple patches to compile and run prop= erly in > > Cygwin. Instead of maintaining them all together as One Big Patch, I f= ind it > > easier to manage them as individual, discrete patch files, and apply th= em all at > > package build time. >=20 > I do that all the time. Just keep the patches in the same directory as > the .cygport, and add their file names (just the basename, no full URI > or path) to PATCH_URI. OK, but what if instead of having my patch files clutter up the top-level directory, I want to keep them tucked neatly away in patches/? (Which I do= .) Will cygport accept PATCH_URI=3Dpatches/* ? > > I also have extra files, such as README and setup.hint, that I like to = just copy > > in before building, instead of maintaining them as patches. Again, thi= s is > > easier for me in the long run. >=20 > I don't think anybody maintains these as a patch; just copy them into > CYGWIN-PATCHES sometime before the install step. I prefer to do this > manually so that I'm sure to check/update them before packaging. I prefer to do it automatically, so I don't forget or have to do it manually every time I rebuild (which I sometimes repeat several times from scratch, = for the same pkg-ver-rel). So should I do that at the start of src_compile(), = or is there a better place? Thanks, Andrew.