Subject: Re: What does the "WRKOBJDIR" variable do?
To: Rakhesh Sasidharan <rakheshster@gmail.com>
From: Geert Hendrickx <ghen@NetBSD.org>
List: pkgsrc-users
Date: 06/03/2006 15:03:05
On Sat, Jun 03, 2006 at 04:49:45PM +0400, Rakhesh Sasidharan wrote:
> >On Sat, Jun 03, 2006 at 04:33:49PM +0400, Rakhesh Sasidharan wrote:
> >> Assuming "WRKOBJDIR=/somewhere/else/pkgsrc-obj" and pkgsrc tree is
> >> writeable, then "/somewhere/else/pkgsrc-obj/mail/spamassassin/work/"
> >> will be a symbolic link to "/path/to/pkgsrc/mail/spamassassin/work/"
> >> eh? So if pkgsrc is writeable, then there's no real advantage of
> >> setting WRKOBJDIR ...
> >
> >There is.  E.g. my /tmp filesystem is on tmpfs (NetBSD-current) and I
> >have WRKOBJDIR=/tmp/work, which is much more efficient.
> 
> If "/tmp/work" points to "/path/to/pkgsrc/editors/nano/work", then
> what advantage do we have if "/tmp" is on tmpfs? I'd have assumed all
> the actual work happens in "/path/to/pkgsrc/editors/nano/work" and so
> "/tmp" shouldn't make any difference .... am I understanding something
> wrong here? :-S

It's the other way around; /path/to/pkgsrc/editors/nano/work is a
symlink to /tmp/work/editors/nano/work, so none of the temporary build
files ever hits my disk.  

(additionally, I have CREATE_WRKDIR_SYMLINK=NO in /etc/mk.conf to make
my pkgsrc dir completely read-only.)  

	Geert