From owner-cvs-all@FreeBSD.ORG Wed Aug 16 21:30:13 2006 Return-Path: X-Original-To: cvs-all@FreeBSD.org Delivered-To: cvs-all@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E96316A4DA; Wed, 16 Aug 2006 21:30:13 +0000 (UTC) (envelope-from sobomax@FreeBSD.org) Received: from sippysoft.com (gk.360sip.com [72.236.70.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id B48BF43D46; Wed, 16 Aug 2006 21:30:12 +0000 (GMT) (envelope-from sobomax@FreeBSD.org) Received: from [192.168.1.56] ([204.244.149.125]) (authenticated bits=0) by sippysoft.com (8.13.6/8.13.6) with ESMTP id k7GLU9ZN026918 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Aug 2006 14:30:10 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Message-ID: <44E38E2F.4000005@FreeBSD.org> Date: Wed, 16 Aug 2006 14:29:19 -0700 From: Maxim Sobolev Organization: Sippy Software, Inc. User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: Erwin Lansing References: <200608041234.k74CYoc1076722@repoman.freebsd.org> <44E389AA.3000003@FreeBSD.org> In-Reply-To: <44E389AA.3000003@FreeBSD.org> Content-Type: text/plain; charset=KOI8-U; format=flowed Content-Transfer-Encoding: 7bit Cc: cvs-ports@FreeBSD.org, FreeBSD Developers , cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/Mk bsd.emacs.mk bsd.gnome.mk bsd.mail.mk bsd.openssl.mk bsd.port.mk bsd.port.subdir.mk bsd.python.mk bsd.ruby.mk bsd.scons.mk ports/Tools/scripts security-check.awk ports/databases/p5-DBD-Oracle Makefile ports/databases/p5-sqlrelay ... X-BeenThere: cvs-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the entire tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Aug 2006 21:30:13 -0000 Maxim Sobolev wrote: > I think the solution proposed in PR/100555 is overengineered. Why not to > build temporary binary package as usually and then use chroot(8) (or -C > flag for pkg_install) to install it into DESTDIR environment? This would > be *much* simpler approach and it won't require modifying anything but > bsd.port.mk. Putting additional load on port maintainers on keeping > their ports DESTDIR-clean is too much for such a niche feature. Just to make clean: what I am proposing is the following course of actions when DESTDIR is defined: 1. Build port as usually. Install it as usually. 2. After usual installation is complete build temporary binary package out of it and install it into DESTDIR environment. Automating it would require some amount of work, granted, but it would be one time task, not constant burden on port maintainers. -Maxim