Here’s a link to a commit for dsynth that gives an idea of how huge a debug build of chromium can be.
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.
DragoFly 6.0 is tagged and ready for download. There’s ISO images and of course you can upgrade using the notes on the release page. One of the improvements in this release cycle is improved dsynth support, so of course there are many prebuilt packages available; don’t forget to update those too.
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’ve mentioned it before but it came up again, so it’s worth repeating: your 5.8 install of DragonFly may need an update of the pkg tool.
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.
Because there’s a newer version of sh(1) in DragonFly, you may need to update your 5.8 system to continue building ports from source. Binary installation through pkg still works as expected so this may not 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.
The short answer is: works great. The version in dports lags, cause it’s based on what’s in the FreeBSD package collection, and that’s not updated as quickly.
This is technically the prerelease, since the official one is a few months off. TeX Live binaries can be downloaded directly for DragonFly.
This happened a little bit ago but I wanted to be able to post a solution to the pkg upgrade issue (yesterday) before mentioning it: there’s a freshly built batch of packages for DragonFly, so now is a good time to upgrade with pkg.
If you upgrade pkg on your system, it may start erroring out. This is because the default config will confuse the newer version. To fix this, you can copy over a working config and the problem will go away. I expect this may only be a problem until the next release.
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.