In Other BSDs for 2018/01/13

A full slate of BSDs this week.

DragonFly 4.9 users and dports

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.

New system: Ravenports

John Marino has assembled a new packaging and building system.  It’s called Ravenports, and he wrote a short intro, and has a filled-out site to go look at.

This is big news, in part because he knows what he’s doing (John worked on dports and created synth) and because it’s cross-platform.  The prior work on synth is part of the reason DragonFly works so well under pressure – the “build everything as fast as possible as complete as possible” strategy makes a great stress test.

There’s no need to change software management strategies yet.  It can be used at the same time as dports, so it doesn’t necessarily change anything for the next DragonFly release.

In Other BSDs for 2017/09/02

Lots of links this week – so many I’ve already started next week’s post.



Near-term dports work

Rimvydas Jasinskas posted an extended description of what’s happening with dports.  There’s a significant xorg reformatting coming in ports, which is going to be absorbed into dports, but it may take some time.  There’s also an odd loss of commit rights for John Marino, who commits (frequently!) to both DragonFly and FreeBSD.  (His followup)  This all translates to some upcoming transition time for dports to accommodate these changes.

Note that if you are using dports binaries, especially on DragonFly 4.6 release, this won’t really affect you; the way dports is set up, binary sets always work.  It is interesting to hear about future work, in any case.

In Other BSDs for 2016/10/22

Oddball links for BSD this week – but pay attention to the first one.

LibreSSL not just available but default

Remember I posted that LibreSSL is in base DragonFly, but not default?  Well, it’s default now.  You can have a system without OpenSSL at all, by rebuilding DragonFly-current and using up-to-date dports.

Update: see John’s comments for clarification: LibreSSL is default; the change is that OpenSSL isn’t even built any more.  The result is still the same good news: you can have an OpenSSL-free DragonFly system now.