I'd like to add a variable like ROOT_INSTALL that if defined as YES, then
the install will change to allow some packages to install outside of the
PREFIX.

For example, I have a lilo package and maybe I want it to install files
to /boot instead of /usr/pkg/boot.

And also I have files that I copy to /bin and /sbin which probably should
be installed there in the first place (like getty, cat, cp, mount, tar,
etc) [1].

I would create alternative PLISTs for this and also create alternative
do-install targets (or whatever is needed for particular packages).

I understand that some +CONTENTS files can have multiple @cwd defined.

This most likely wouldn't be useful for NetBSD, but could be used by
admins of other operating systems who really may want to replace files
under /bin or /sbin, for example.

Any thoughts about this?

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

[1] From textutils, fileutils, bash2, sh-utils, util-linux, ed, gzip-base,
shadow, procps, netkit-base, gsed, sysvinit, e2fsprogs, gcpio and
gtar-base (some of which I packaged).

The actual files are like: /bin/cp, /bin/bash, /bin/cat, /bin/chgrp,
/bin/chmod, /bin/chown, /bin/cp, /bin/cpio, /bin/date, /bin/dd, /bin/df,
/bin/dmesg, /bin/echo, /bin/ed, /bin/false, /bin/gunzip, /bin/gzip,
/bin/hostname, /bin/kill, /bin/ln, /bin/login, /bin/ls, /bin/mkdir,
/bin/mknod, /bin/more, /bin/mount, /bin/mv, /bin/netstat, /bin/ping,
/bin/ps, /bin/pwd, /bin/rm, /bin/rmdir, /bin/sed, /bin/bash, /bin/stty,
/bin/su, /bin/sync, /bin/tar, /bin/touch, /bin/true, /bin/umount,
/bin/uname, /bin/zcat, /sbin/fdisk, /sbin/fsck, /sbin/fsck.*,
/sbin/agetty, /sbin/halt, /sbin/ifconfig, /sbin/init, /sbin/mkfs,
/sbin/mkfs.*, /sbin/mkswap, /sbin/reboot, /sbin/route, /sbin/shutdown,
/sbin/swapoff, /sbin/swapon.

I currently do this with a meta-package and an INSTALL script to copy into
place.