Date: Wed, 16 Aug 2006 12:14:29 -0600 From: John E Hein <jhein@timing.com> To: Kris Kennaway <kris@obsecurity.org> Cc: babak@farrokhi.net, amdmi3@mail.ru, G??bor K??vesd??n <gabor@FreeBSD.org>, freebsd-ports@FreeBSD.org Subject: Re: DESTDIR implementation [Was:: ATTENTION: is the way DESTDIR was introduced completely wrong?] Message-ID: <17635.24709.983143.540440@gromit.timing.com> In-Reply-To: <20060816173628.GA14848@xor.obsecurity.org> References: <20060814234414.GA57035@hades.panopticon> <44E194BA.2020507@FreeBSD.org> <17634.5246.887894.836856@gromit.timing.com> <20060816173628.GA14848@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote at 13:36 -0400 on Aug 16, 2006:
> mount_nullfs ${PORTSDIR} ${DESTDIR}${PORTSDIR}
> mount_nullfs ${WRKDIR} ${DESTDIR}${WRKDIR}
> mount_devfs foo ${DESTDIR}/dev
> chroot ${DESTDIR} cd ${.CURDIR} && make install
>
> A suitable version of the above should allow all ports to be installed
> into a jail-ready filesystem hierarchy, while requiring 0 port
> changes.
I do that, too - we _have_ to since DESTDIR never worked right.
That's more heavyweight than a DESTDIR chroot (which doesn't need to
have much more than pkg* tools & libc & a few others), but that's a
very minor advantage over a full chroot (and probably not worth trying
to special case). My original DESTDIR "fix" didn't involve a chroot
at all, but runs into problems with pkg management.
Note that if we go that route (just run completely within a chroot),
we might as well just rip DESTDIR support out of Mk/*.mk altogether.
That would be better than the "fake" support for DESTDIR.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?17635.24709.983143.540440>