This note from James Cook describes how to get Wireguard functioning on DragonFly; his linked patch is not necessary at this point since it’s been committed to dports – though not in the latest binaries.
Thanks to yrabbit, there’s a full FPGA toolchain possible on DragonFly. It’s preliminary, but it works.
I’m actually some days late in reporting this, but there’s a new full build of packages for DragonFly 6.0; it’s following the quarterly release schedule for ports, so 2021Q2 is the base.
This goes with the recent merges from -current into 6.0. Now is a good time to update your system completely, if you have not already.
If you are upgrading an older 5.8.x system to DragonFly 6, and get a lua error when updating pkg: manually copy over a config file, and you’ll be set.
With good timing, 6.x packages are now available for those of you who need them.
There’s a new build of binary packages available, for both 5.8 and DragonFly-current.
I was sure I had posted a link to this before, but apparently not: “How to install DragonFly BSD 5.6.1 plus MATE and some aplications” (Youtube, via)
If you’re running on DragonFly master, make sure you are on the right version of bmake. If you are on 5.8, it won’t affect you.
There’s a new build of DragonFly 5.8 binary packages available. There’s a sudo fix in there for the recent public cross-platform CVE it had, plus the linked announcement describes how to get around a pkg upgrade bug.
I’m not sure if this is directly helpful, but a recent series of posts about running jitsi on DragonFly covers the different parts of setting it up. There isn’t a “this is the solved answer” post to point at; I’m linking to the start of the thread as it might be useful for someone.
If you delete all your installed packages, you will also lose the certificate used by pkg to verify the connection to download new ones. There’s several workarounds for this problem.
A complete set of new dports binaries have been built, for 5.8 and for -current, so now is a good time to upgrade. Update to 5.8.3 if you haven’t yet, while you are at it.
Here’s a recommendation (and a usage lesson) on pkg-provides, a tool for matching a file to the installed pkg that brought it. It goes with the pkglocate article some weeks ago; it seems like this should be standard functionality. Thanks to Nelson H. F. Beebe.