From owner-freebsd-ports@FreeBSD.ORG Fri Jan 16 16:00:25 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1C2CB67B for ; Fri, 16 Jan 2015 16:00:25 +0000 (UTC) Received: from vm.unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id D4563634 for ; Fri, 16 Jan 2015 16:00:24 +0000 (UTC) Received: from vhoffman.lon.namesco.net (lon.namesco.net [195.7.254.102]) by vm.unsane.co.uk (Postfix) with ESMTPSA id 0F5DC30197; Fri, 16 Jan 2015 16:00:24 +0000 (GMT) Message-ID: <54B93597.9080808@unsane.co.uk> Date: Fri, 16 Jan 2015 16:00:23 +0000 From: Vince Hoffman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0 MIME-Version: 1.0 To: papowell@astart.com, freebsd-ports@freebsd.org Subject: Re: BIND REPLACE_BASE option References: <2A3ABE9AE68B3CE8E1B7C1A1@ogg.in.absolight.net> <20150113163324.299F27E9@hub.freebsd.org> <20150114080033.GE33449@droso.dk> <20150114153427.63AD7C0A@hub.freebsd.org> <54B696BF.5020901@FreeBSD.org> <20150114163443.280B1ED9@hub.freebsd.org> <20150115084803.GM33449@droso.dk> <20150115170017.3CB64A96@hub.freebsd.org> <54B9336D.6090901@astart.com> In-Reply-To: <54B9336D.6090901@astart.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Jan 2015 16:00:25 -0000 On 16/01/2015 15:51, Patrick Powell wrote: > On 01/15/15 09:00, Roger Marquis wrote: >>> This sounds like you, like many other people have done in the past, >>> have >>> built an in-house solution based on the tools available at the time, >>> which includes 'make package' >> >> I wouldn't call it an in-house solution since the package target is a >> feature of the ports infrastructure. We simply 'make package' and >> install other systems from the resulting package. >> >> This does not, however, appear to be as well supported by portsng/pkgng >> as it was in the previous versions. Now it just exits with no message >> and a 0 exit-code without creating the package unless you've created >> /usr/ports/packages and/or specified one or more of WRKDIRPREFIX, >> PACKAGES and PKGREPOSITORY. >> >> What documentation there is seems to be based on older versions (like >> much of the FreeBSD website) and I haven't found anything on the >> differences between 'make package' and Poudriere. >> >> Roger >> _______________________________________________ >> freebsd-ports@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" >> > This is actually a side effect of the STAGING implementation. The > package file is put into the > port (created) work sub directory. Now if I could only find the > documentation that tells me how to put, say, > WORK_DIRECTORY=/var/tmp/work into the /etc/make.conf file or > something similar I would be > a very (well, not so grumpy) happy camper. I read this somewhere once > but I cannot find > it again. WRKDIRPREFIX? WORKDIRPREFIX? > >From looking in /usr/ports/Mk/bsd.port.mk I think you want to set one of the following in make.conf # WRKDIRPREFIX - The place to root the temporary working directory # hierarchy. # Default: none # WRKDIR - A temporary working directory that gets *clobbered* on clean # Default: ${WRKDIRPREFIX}${.CURDIR}/work not the most intuitive place to look but I guess thats why the BUGS section of PORTS(7) says BUGS Ports documentation is split over four places -- /usr/ports/Mk/bsd.port.mk, The Porter's Handbook, the ``Packages and Ports'' chapter of The FreeBSD Handbook, and this manual page. Vince