Date: Wed, 16 Aug 2006 14:29:19 -0700 From: Maxim Sobolev <sobomax@FreeBSD.org> To: Erwin Lansing <erwin@FreeBSD.org> Cc: cvs-ports@FreeBSD.org, FreeBSD Developers <developers@FreeBSD.org>, 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 ... Message-ID: <44E38E2F.4000005@FreeBSD.org> In-Reply-To: <44E389AA.3000003@FreeBSD.org> References: <200608041234.k74CYoc1076722@repoman.freebsd.org> <44E389AA.3000003@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44E38E2F.4000005>