can you PLEASE _read_ the QAT mails? (was: Re: Question about a failure report)

[Ion-Mihai Tetcu]

On Thu, 9 Jul 2009 22:25:50 +0200
Ulrich Spörlein <uqs at spoerlein.net> wrote:

> On Mon, 06.07.2009 at 00:51:48 +0300, Ion-Mihai Tetcu wrote:
> > On Sun, 05 Jul 2009 13:49:49 -0500
> > Paul Schmehl <pschmehl_lists at tx.rr.com> wrote:
> > 
> > > > For short, your port's configure script fails to search for
> > > > mysql headers in the right place; QATty has LOCALBASE and
> > > > PREFIX set to /usr/PPP. If you can't sorted out in a few days
> > > > drop me an email and I'll take a look.  
> > > 
> > > No offense taken.  The thing that confused me is that I always
> > > build my ports in /tmp/portname when testing, but barnyard still
> > > managed to find mysql headers when building. 
> > 
> > Yes, that's PREFIX (ie. you install in /tmp/portname) but LOCALBASE
> > I bet it's /usr/local.
> > 
> > > So I didn't understand why it was failing in QAT.  I followed all
> > > the links in the email and read the materials, but I still didn't
> > > understand why the build failed in QAT.  
> > 
> > It failed on QATty, not on QAT.
> > 
> > QAT has -DNOPORT* while
> > QATty has PREFIX and LOCALBASE = /usr/PPP
> 
> Hi Ion-Mihai,
> 
> this is the first time, I hear there are different QAT setups
> (although it makes sense, doesn't it?). 

Well, QATty is almost at the end (it builds x11/ now) of its first run
(LOCALBASE/PREFIX) conformance :-)
The run was announced on committers ML and on ports ML.

> So I was wondering where this is documented. I am always confused
> about what portsmon is doing vs. pointyhat. 

PortsmMon aggregates the date from PointyHat and a few others sources,
it's usually easier to use that PointyHat directly.

> Then we have tinderbox for src and other ones for ports. Now there
> are multiple QAT setups!

And we're gonna have more! :-)

QAT basically does on-commit testing (I regard -DNOPORT* as something
accessory at the moment since the biggest part of the problems were
fixed).

QATty does non-standard config testing; PREFIX and LOCALBASE for now,
other things in the future.

The plan is to unite reports for on-commit testing, for standard
config and multiple non-standard configs and have one QATMail for all
the tests. This depends on available hardware and my available time.

> Searching for 'qat' on wiki.freebsd.org revealed no hits, although I
> think that would be a good place to document all "official"
> port/package "linters"

Blame it on me rather hating wikies. Each QATMail contains a link to a
doc describing the testing process.

> So I would kindly ask you, if you could put some information and links
> regarding QAT on the wiki. Other people will probably fill in the
> details for pointyhat, portsmon, etc.

I'll do it eventually. And yes, you are right, we need to document a
lot of things.


-- 
IOnut - Un^d^dregistered ;) FreeBSD "user"
  "Intellectual Property" is   nowhere near as valuable   as "Intellect"
FreeBSD committer -> itetcu at FreeBSD.org, PGP Key ID 057E9F8B493A297B
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20090709/5c5744e9/signature.pgp