This recent structure change (are there others like this? Maybe?) means that existing binaries may need to be recompiled for anyone tracking DragonFly master. This probably means that an upgrade from 2.10 to 2.12 will require rebuilds of all binary pkgsrc packages.
A running description of activity related to DragonFly BSD.
No may but will require rebuilds of all x64 binary pkgsrc.
Typo: No -> Not
What I did was
* update with pkgin to the latest pkgsrcr elease for the new OS version
dfly-bkpsrv# cat /usr/pkg/etc/pkgin/repositories.conf
#http://avalon.dragonflybsd.org/packages/i386/DragonFly-2.5/stable/All
#http://avalon.dragonflybsd.org/packages/i386/DragonFly-2.7/pkgsrc-2010Q2/All
#http://avalon.dragonflybsd.org/packages/i386/DragonFly-2.11/pkgsrc-2011Q2/All
#http://avalon.dragonflybsd.org/packages/i386/DragonFly-2.13/pkgsrc-2011Q3/All
# pkgin update
# pkgin full-upgrade
* use pkg_rolling_replace for the rest of the stuff.
# cd /usr/pkgsrc && git pull
# pkgsrc-2011Q3
# pkg_rolling-replace -rsuv
I still had to recompile samba though it was upgraded using pkgin because of libkrb5 error similar to.
https://bbs.archlinux.org/viewtopic.php?id=51673