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.
As part of installing DragonFly, Jonathan Engwall happened to create a script to install every part of xfce4 that he wanted. I’m linking to it in case you want it too.
(xorg and web browser install not included)
A note for the future: if pkg itself isn’t working, you can use pkg-static.
This is I think not resolved yet, but here’s something I didn’t know: keeping Chromium from being tied into Google’s services is actually a build issue, not a settings issue. i.e. once it’s in binary form, you can’t opt out.
On EFNet #dragonflybsd, Matthew Dillon and ‘mjg’ have been discussing various way to optimize for bulk builds. A recent update from mjg for different memory functions shaved 1.7% off bulk build time – significant, when you are talking tens of thousands of packages.