The more eagle-eyed may have noticed a branching for DragonFly 4.2, and for DragonFly 4.0.6. The 4.2 branch is currently only a release candidate, so don’t necessarily change over yet – it’s for testing, not release. Note that packages for 4.2 are not yet built, so you’ll have to manually specify a package path to install with pkg on 4.2 – for now.. That won’t be the case for the actual release, of course. DragonFly 4.3 users will have to specify PKG_PATH manually to use 4.2 images until new ones are built. 4.2 release candidate users will be fine. (see comments for correction.)
The 4.0.6 release is mostly to get the recent OpenSSL update into a 4.0.x build.
I am working on image building for both.
“Note that packages for 4.2 are not yet built, so you’ll have to manually specify a package path to install with pkg on 4.2 – for now.. That won’t be the case for the actual release, of course.”
This is pretty much 100% false.
packages for 4.2 have been available for MONTHS. The newest is only a couple of days old. packages for 4.4 (dev branch 4.3) are not available. Those people will need to specify 4.2.
I would have thought “4.2” was a typo, but the last clause “won’t be the cause for actual release” makes no sense, unless you are talking about the 4.4 release in 6 months.
I think the entry should be re-written because it’s misleading in a way that can cause real confusion.
FYI: http://avalon.dragonflybsd.org/dports/dragonfly:4.2:x86:64/
Hm. I thought they weren’t built, and there was already two people on IRC saying “I built 4.2 and pkg doesn’t work”, meaning that they couldn’t download images with it. Maybe they were actually on master or I’m misremembering.
I haven’t had an image to test, though I plan to later today. Article is corrected.