On Fri, Mar 23, 2012 at 11:25:49AM +0000, Stuart Henderson wrote: > On 2012/03/23 07:11, RD Thrush wrote: > > My PORTSDIR is on an nfs server. Mounting the particular nfs > > directory on /usr/ports (and setting PORTSDIR accordingly) fails the > > new test in bsd.port.mk. > > > > Apparently test -h considers an nfs mount the same as a symlink... > > Hmm, that's weird. It doesn't for me, my PORTSDIR is on an NFS server > and it works fine with -current bsd.port.mk. > > Probably better to work out why test is broken for you.
Like Stuart said, there's a bug in your install. Maybe your symlink hides behind the NFS mount ? Your corrected test is no good, we want to avoid symlinks because some ports won't build when /usr/ports is a symlink AND PORTSDIR is not set to the real directory (net/poco, www/chromium, some flavors of net/avahi) Chances are those don't build for you. Try configuring chromium, for instance.
