Date: Tue, 25 Dec 2001 23:52:48 -0500 From: Pete Fritchman <petef@databits.net> To: Alan Eldridge <alane@geeksrus.net> Cc: FreeBSD Ports List <ports@freebsd.org> Subject: Re: Re; Porting & Makefiles Message-ID: <20011225235248.D17861@databits.net> In-Reply-To: <20011226043805.GA67287@wwweasel.geeksrus.net>; from alane@geeksrus.net on Tue, Dec 25, 2001 at 11:38:06PM -0500 References: <20011226043805.GA67287@wwweasel.geeksrus.net>
next in thread | previous in thread | raw e-mail | index | archive | help
++ 25/12/01 23:38 -0500 - Alan Eldridge:
| I can think of one reason that the MAKEFILE=${FILESDIR}/Makefile trick
| might not be best: if you're modifying or debugging a ported program, you
| may well want to run make manuall, in $WRKSRC. In that case, Steve's use of
| a post-patch: target is better (and beats my suggestion of a pre-build
| target as well).
Yes, but if you're modifying or debugging a port by doing manual stuff
in ${WRKSRC}, you probably have a clue how ports work and will figure
this out :) You'll also run into tons of problems if there are custom
MAKE_{ARGS,ENV}, etc. I don't think we need to account for this.
-pete
--
Pete Fritchman [petef@(databits.net|freebsd.org|csh.rit.edu)]
finger petef@databits.net for PGP key
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011225235248.D17861>