Why Are You NOT Using FreeBSD?

[Mark Linimon]

On Mon, Jun 04, 2012 at 07:53:52AM -0400, Michael Scheidell wrote:
> On 6/4/12 7:36 AM, Adam Strohl wrote:
> >Doesn't tinderbox do this every night?

> And, as a committer, here is the point.
> We get reports of 'this doesn't build'.  (no fixed attached, no
> logs, no indication of what was installed first, what options
> taken), [...] So, we run it up in a tinderbox

People who want to understand port failures should be first checking
to see if the port builds in a completely clean environment.  The
best way to do this is to see if it has built on our build cluster
(where a clean environment is forced), and the quickest way to do that
is to use portsmon as a summary of the port across the various buildenvs.
For example:

  http://portsmon.freebsd.org/portoverview.py?category=www&portname=chromium

We can see that chromium is currently having a number of build problems.
It also has a number of PRs filed against it.

On the overview page for each port are links to both CVSWeb, as well
as the information FreshPorts displays for the port:

  http://www.freebsd.org/cgi/cvsweb.cgi/ports/www/chromium/
  http://www.freshports.org/www/chromium

So I recommend that we suggest to people who are having problems with a
particular port use portsmon as a "start here" resource.

mcl