On Mon, 11 Aug 2008 09:55:49 -0400, Ted Unangst wrote > Since the people building the release are building the release, it's > pretty likely they'll find out all on their own.
True. A couple of points which perhaps weren't articulated well at the beginning of this thread: First, -release is nothing more than a carefully crafted snapshot. Second, OPENBSD_4_4 is a -stable tag, not -release. Third, OPENBSD_4_4_BASE builds without trouble, *if* one approaches the process with due care. So far it builds fine on i386 and sparc64. > > If there's a better venue for such reports, lets have it :) > > Since 90% of compilation failures are user error, the best venue is > probably reading the instructions again. Since 4.4-release is not yet supported, *no* appropriate venue exists. Note that source upgrades are always unsupported, too. The proper recourse is to blame the user-in-the-mirror for any resulting problems from leaving the supported path. In my case, I happen to use the tagged -release in order to build a set of -release LiveCDs/LiveDVDs with sufficient time to get them adequately tested and available for download on the scheduled public -release date.
