From owner-freebsd-ports Fri Aug 7 15:32:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09161 for freebsd-ports-outgoing; Fri, 7 Aug 1998 15:32:23 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from majesticnet.com (host2.majestic.sysci.org [205.227.182.67]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA09156 for ; Fri, 7 Aug 1998 15:32:22 -0700 (PDT) (envelope-from ian@majesticnet.com) From: ian@majesticnet.com Received: (qmail 1254 invoked by uid 509); 7 Aug 1998 22:32:32 -0000 Date: Fri, 7 Aug 1998 15:32:31 -0700 (PDT) Reply-To: ian@majesticnet.com To: Chuck Robey cc: ports@FreeBSD.ORG Subject: Re: patch file question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 7 Aug 1998, Chuck Robey wrote: > The patches are always applied relative to WRKSRC, which is by default > WRKDIR/DISTNAME. You can, of course, play with this, like I did myself > with lang/moscow_ml, if you'd like to see an example. In that case, the > Makefile that needed to get executed wasn't in the main subdirectory, > but instead hidden in a "src" subdirectory. The build target cd's to > the WRKSRC directory to execute the 'make ALL_TARGET', so I changed the > WRKSRC to add the /src component, and that meant that my patches had to > be relative to the src subdirectory, instead of the normal "mosml" > directory that the tar file unpacked into. That is what I thought. I just wanted to be sure before I adjust some of the patchfiles and send off some diffs to the maintainer of the ldap port. As they stand right now, there is one very large patch file that is relative to WRKDIR and 11 patches relative to WRKDIR/DISTNAME. If I get a chance this weekend, I hope to modify the weird (relative to WRKDIR) patch to be the same as the others. Thanks for the clarification on this, (Satoshi too) Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message