Should .buildlink-x11 (or .x11-buildlink) ever be different from
.buildlink?

Is there ever a reason or use of having separate work/.*buildlink*
directories?

Why do we have symlinks for the .x11-buildlink (or .buildlink-x11)
directories? Why not just use the .buildlink for all?

My experiment is now with NetBSD/i386 1.6.2_RC3 using
X11BASE == LOCALBASE (/usr/pkg) without using xpkgwedge.

This was successful this far:

bigfour:/usr/pkgsrc/www/epiphany$ pkg_info -K /var/db/pkg3
digest-20021220     Message digest wrapper utility
sudo-1.6.7.5        Allow others to run commands as root
xdg-dirs-1.0        Shared XDG directories
gnome-dirs-1.2      Shared GTK/GNOME (v1 and v2) directories
gnome2-dirs-1.2nb1  Shared GTK/GNOME (v2) directories
gethost-0.03        Hostname and IP resolver for testing /etc/hosts and
nsswitch
perl-5.6.1nb10      Practical Extraction and Report Language
libtool-base-1.4.20010614nb19 Generic shared library support script (the
script itself)
libiconv-1.9.1nb1   Character set conversion library
pth-2.0.0           GNU Portable Thread library
pkgconfig-0.15.0    System for managing library compile/link flags
gmake-3.80nb2       GNU version of 'make' utility

But once I tried to use something with buildlinking of X, it fails:

bigfour:/usr/pkgsrc/devel/glib2$ ls -ld work.bigfour/.buildlink*
drwxr-xr-x  6 reed  wheel  512 Feb  5 10:46 work.bigfour/.buildlink
drwxr-xr-x  4 reed  wheel  512 Feb  5 10:46 work.bigfour/.buildlink-x11
-rw-r--r--  1 reed  wheel    0 Feb  5 10:46 work.bigfour/.buildlink_done

The configure failed with:

ld: cannot find -liconv

The libiconv libraries are not in work/.buildlink but in the separate (no
symlink) .buildlink-x11 directory.

One workaround I have used previously is to set
BUILDLINK_X11_DIR to same as BUILDLINK_DIR.

What is the best way to handle this?

Thank you,

   Jeremy C. Reed
   http://bsd.reedmedia.net/