Pages
  • life with BSD
  • 2025-12-23 Understanding more about the pkg-status service for FreeBSD
  • 2025-12-07 Trying out flow control binaries for FreeBSD
  • 2025-11-07 Swift nightly preview for FreeBSD
  • 2025-11-02 Using jujutsu in a git compatible way to track freebsd ports
  • 2025-10-28 The sherlocking of the gemini protocol
  • 2025-10-09 How to change the options in a freebsd port
  • 2025-09-16 Waiting on Swift mainline for FreeBSD
  • 2025-08-25 Dmesg for Cable Matters USB 3.1 to 4 port Gigabit Ethernet Adapter
  • 2025-08-15 Generate a QR code with typst
  • 2025-07-31 Fixing jujutsu and leaky ascii escape sequences on FreeBSD
  • 2025-07-31 Swift now available as a package for FreeBSD
  • 2025-07-28 The FreeBSD project clarifies its stance on gen-ai powered contributions
  • 2025-07-28 The rustup question
  • 2025-07-08 Goodbye old friend, a tale
  • 2025-06-30 Configuring FreeBSD to network with a postmarketos phone over usb
  • 2025-06-25 swift (re)lands in the FreeBSD ports tree
  • 2025-06-24 typst a rust powered typesetting tool aiming at latex
  • 2025-06-19 Open Source Two Worlds thoughts
  • 2025-06-14 Taking a look at repolocli
  • 2025-06-09 Zig master builds now with FreeBSD support
  • 2025-06-07 Finding rust dependencies in Makefile.crates
  • 2025-06-05 Ripgrep or ripgrep-all
  • 2025-06-02 Ripgrep a nice Rust utility for ports spelunking
  • 2025-05-31 Get started with gpui on FreeBSD
  • 2025-05-29 Query freshports with Deno
  • 2025-05-27 Trying out Defuddle an npm tool via Deno
  • 2025-05-25 Deno for FreeBSD
  • 2025-05-23 A new beginning
life with BSD
  • life with BSD
  • 2025-12-23 Understanding more about the pkg-status service for FreeBSD
  • 2025-12-07 Trying out flow control binaries for FreeBSD
  • 2025-11-07 Swift nightly preview for FreeBSD
  • 2025-11-02 Using jujutsu in a git compatible way to track freebsd ports
  • 2025-10-28 The sherlocking of the gemini protocol
  • 2025-10-09 How to change the options in a freebsd port
  • 2025-09-16 Waiting on Swift mainline for FreeBSD
  • 2025-08-25 Dmesg for Cable Matters USB 3.1 to 4 port Gigabit Ethernet Adapter
  • 2025-08-15 Generate a QR code with typst
  • 2025-07-31 Fixing jujutsu and leaky ascii escape sequences on FreeBSD
  • 2025-07-31 Swift now available as a package for FreeBSD
  • 2025-07-28 The FreeBSD project clarifies its stance on gen-ai powered contributions
  • 2025-07-28 The rustup question
  • 2025-07-08 Goodbye old friend, a tale
  • 2025-06-30 Configuring FreeBSD to network with a postmarketos phone over usb
  • 2025-06-25 swift (re)lands in the FreeBSD ports tree
  • 2025-06-24 typst a rust powered typesetting tool aiming at latex
  • 2025-06-19 Open Source Two Worlds thoughts
  • 2025-06-14 Taking a look at repolocli
  • 2025-06-09 Zig master builds now with FreeBSD support
  • 2025-06-07 Finding rust dependencies in Makefile.crates
  • 2025-06-05 Ripgrep or ripgrep-all
  • 2025-06-02 Ripgrep a nice Rust utility for ports spelunking
  • 2025-05-31 Get started with gpui on FreeBSD
  • 2025-05-29 Query freshports with Deno
  • 2025-05-27 Trying out Defuddle an npm tool via Deno
  • 2025-05-25 Deno for FreeBSD
  • 2025-05-23 A new beginning

2025-12-23 Understanding more about the pkg-status service for FreeBSD

If you're interested in porting software for FreeBSD and not afraid to jump into code aspect then keeping the FreeBSD Porters Handbook on your bookmark list. This explains many of the mechanics and the actual on the ground work for packaging up a port for FreeBSD. Note that there is copious amount of documentation for FreeBSD such that it can be daunting for a newcomer to FreeBSD to sort it out all. If you're just starting to USE FreeBSD, I think you can't go wrong with going to the FreeBSD Handbook which focuses on using FreeBSD rather than developing or packaging software for FreeBSD.

Assuming you've got a port submitted and want to continue to maintain it. At some point you might learn about the pkg-fallout report. The FreeBSD project runs continuous builds (the other more modern term is CI) to periodically check that the ported software can still build and reports are generated from that. Note that this information is located here in the Committer's Guide rather than the Porters Handbook (as I originally assumed).

If you hear from pkg-fallout one of the sites you might stumble across is https://pkg-status.freebsd.org/ which has (extensive) information on ports builds for FreeBSD. Decoding all the information for pkg-status is pretty daunting for newcomers to this service. One thing I noticed is there is a Type field for the different types of builds which are labeled:

  • exp

  • package

  • qat

After staring at that for awhile, I tried to find some documentation that explained how to make sense of the interface and came across this guide that was helpful in understanding a little more. Unfortunately, not much information regarding the Type. After puzzling for awhile, my guess is that they mean the following (could be wrong):

  • exp - Experimental

  • package - Package builds

  • qat - Quarterly package builds

References

  • Using package build records at pkg-status.freebsd.org

  • The FreeBSD Handbook

  • FreeBSD Porters Handbook

  • Committer's Guide

PREVRANDOMNEXT