Category: DPorts

The binary package repository for DragonFly-current has been updated with the latest build of all packages, thanks to tuxillo and others on EFNet #dragonflybsd doing a lot of work.

Tuxillo noted: there’s new rust, thunderbird, firefox, nginx, several llvm versions, and a new chrome (version 72).  freerdp is temporarily broken; use remmina with the rdp plugin instead.  openvpn isn’t upgraded yet cause the build was with libressl, which is a broken combination – it’ll all be built with openssl in a future run.

Issues go here, submissions of work go there.

As mentioned last week, there’s a new build of dports for 5.4, now available.  No surprise, but a reminder to keep third-party software up to date is never wasted.

Thanks to tuxillo and others, there’s a new build of dports on the way for DragonFly 5.4 that includes packages that weren’t building before – mongodb, kodi, mysql80, and I imagine more that I don’t know about.  If the synth build is still running when you read this, you can look at its status page.  If it isn’t running, the packages are of course in the normal place and you can use ‘pkg upgrade’ to get them.

A little while back I linked to an excellent deep dive into Ravenports, and added my own bit of statistical guessing at popular packages.  John Marino wants to know what packages people find most useful/most required.  If you have opinions, and I’m sure you do, post something on the Ravenports Google Groups page.

If you are saying to yourself “Gee, what packages did I install and what came in as a dependency?”, here’s an easy way to find out:

pkg query -a '%n %a' | grep 0 | cut -d ' ' -f 1 | less

This lists all “vital” packages, which usually means ones installed with intent, rather than automatically.  This might be a useful thing to post for Ravenports…

There’s a plugin for pkg, called pkg-provides, which will tell you what package(s) contain the filename you provide – installed or not.  I didn’t even know pkg had a plugin system.  Anyway, it works on DragonFly, as the author notes.

Because of the major version number change, there’s no packages built for DragonFly 4.9.  Your options are to either update to 5.1 (which you probably meant to do anyway if you are running current) or manually point to the newest packages.  Or just build from dports.

For clarity, this does not affect you at all if you are running 5.0 release.  It only affects you if you are running DragonFly-current and have not updated in a while.