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 ...

Max Khon fjoe at samodelkin.net
Sat Sep 2 12:45:56 UTC 2006


Hi!

On Wed, Aug 16, 2006 at 11:44:13PM +0200, G??bor K??vesd??n 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
> I don't think it would be good, since:
> 
> 1, The package building requires that the package be installed first, 
> and we don't want to make the host environment dirty in such way.

I think this should be fixed. Nobody else requires package to be installed
first.

/fjoe


More information about the cvs-ports mailing list