HEADS UP: structure changes, pkgsrc changes

Two things:

  1. If you are running DragonFly 2.7, Matthew Dillon has made some kernel changes, so updating your 2.7 machine will require a full buildworld cycle, not quickworld.
  2. The binary packages for 2.6 and 2.7 have been updated to pkgsrc-2010Q2.  This means that pkg_radd will automatically pull down newer packages, and you should make sure your /usr/pkgsrc is using the pkgsrc-2010Q2 release if you want to be sure there’s no version mismatches.

I recently sent out a description of what built for pkgsrc-2010Q2 , though the section on not changing the stable link is no longer true.

Messylaneous – Unixy articles, clang, pkgsrc projects, more
3 things for pkgsrc

From my email to users@:

  • I almost have pkgsrc-2010Q1 builds done for every architecture, so I’ll point the default load location for pkg_radd to them within the next 24 hours.
  • Are you still using a DragonFly system older than 2.4 and downloading binaries?  If so, tell me.
  • A project: enhancing pkg_search and pkg_radd to be able to tell when a package is missing because of license restrictions.  Anyone want to try it?
What does DESTDIR mean?

I’ve made reference to DESTDIR for pkgsrc several times, with only an informal understanding of what it means.  From what I’ve learned, and what Joerg Sonnenberger’s told me, DESTDIR support means that packages can be built from pkgsrc without needing to be root.  This means local packages can be built on an ordinary user account using pkgsrc.

This also means that pkgsrc can build packages before each upgrade, and only upgrade if a binary package can be built for each item involved.  This means minimal downtime and no failures during upgrades, the biggest bugaboo for using pkgsrc that I’ve encountered.