1. 11

  2. 1

    This is wonderful, I now run -stable both on router and workstation (was always on -current before), in part because of this.

    Thanks M:Tier!

    1. [Comment removed by author]

      1. 3

        My biggest problem running -current on servers is usually that 3 months down the road, I’ll need to install some random package. The packages for that snapshot are gone from the mirrors, the previous release’s and the current snapshot’s packages have different system library version dependencies so they’re not compatible. Now I need to either:

        a) upgrade the server to the newest snapshot, forcing a reboot and bringing it back up in production with a possibly not-so-stable snapshot (or just one that has incompatible changes) that I can’t easily roll back from, or

        b) download the whole ports tree to compile the one port I need, which usually brings with it a bunch of stupid build dependencies that have to fetch, build, and install. Fetching the ports tree with a -D spec of the snapshot’s date helps avoid system/version incompatibilities, but it’s still a pain in the ass to deal with all of this just to get one package installed that on a stable release would just be a pkg_add away.

        1. 1

          For the base sets I agree, but I use xombrero for web browser, and more often than not it is severely crashing on -current (varies with each new packages rollout). On -stable I get much less of it. Firefox is generally stable but I don’t want to use it.

          Knowing me, I won’t be able to resist the temptation for so long anyway but I will try. Six months between reinstalls has some zen-like appeal to it. Plus, I will notice much bigger difference/improvement with official releases.