Date: Wed, 16 Aug 2006 20:14:08 +0200 From: =?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?= <gabor@FreeBSD.org> To: Kris Kennaway <kris@obsecurity.org> Cc: babak@farrokhi.net, amdmi3@mail.ru, John E Hein <jhein@timing.com>, freebsd-ports@FreeBSD.org, Erwin Lansing <erwin@FreeBSD.org> Subject: Re: DESTDIR implementation [Was:: ATTENTION: is the way DESTDIR was introduced completely wrong?] Message-ID: <44E36070.4080007@FreeBSD.org> In-Reply-To: <20060816180646.GA79702@xor.obsecurity.org> References: <20060814234414.GA57035@hades.panopticon> <44E194BA.2020507@FreeBSD.org> <17634.5246.887894.836856@gromit.timing.com> <20060816173628.GA14848@xor.obsecurity.org> <44E35C08.3020502@FreeBSD.org> <20060816180646.GA79702@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote:
> On Wed, Aug 16, 2006 at 07:55:20PM +0200, G?bor K?vesd?n wrote:
>
>> Kris Kennaway wrote:
>>
>>> On Tue, Aug 15, 2006 at 12:37:50PM -0600, John E Hein wrote:
>>>
>>>
>>>
>>>> The hard part is to get ports writers to think the right way about
>>>> DESTDIR after ignoring it for so many years. And once you decide to
>>>> go about fixing it, there's no way around that problem.
>>>>
>>>>
>>> My preferred solution involves a couple of shell commands, along the
>>> lines of the following:
>>>
>>> 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.
>>>
>>> Kris
>>>
>>>
>> This makes sense, but I did not succeed to use mount_nullfs on an
>> 5.3-RELEASE/amd64 machine, while the same worked well on my 6.1/i386
>> computer, so I'm not sure mount_nullfs is reliable enough on older systems.
>>
>
> Who cares about old systems that are already unsupported and will only
> become even more unsupported over time? Nullfs works in 6.x and will
> continue to work in the future (since I use it extensively and yell at
> whoever breaks it ;-)
>
>
>> Also, other targets should be supported as well, and the nullmounted
>> directory should be umounted after he run. Anyway, I find this solution
>> very good, if we can work this out a bit better, my progress so far
>> would become pointless...
>>
>
> It's a shame to throw away your work, but IMO it would also be a
> bigger shame not to proceed if a simpler solution can be made to work.
>
> Kris
>
Agreed. I just feel a bit guilty, since I made things complicated and
obscure, while I just want to provide a good solution, but haven't
thought of mount_nullfs.
--
Cheers,
Gabor
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44E36070.4080007>