pcp
[Top] [All Lists]

Re: [pcp] pcp updates: some build/package re-jigging and QA

To: Nathan Scott <nathans@xxxxxxxxxx>, Lukas Berk <lberk@xxxxxxxxxx>
Subject: Re: [pcp] pcp updates: some build/package re-jigging and QA
From: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Date: Mon, 16 Nov 2015 06:38:08 +1100
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <2108185319.9113269.1447193300260.JavaMail.zimbra@xxxxxxxxxx>
References: <563949B8.9020604@xxxxxxxxxxxxxxxx> <87d1vn81w8.fsf@xxxxxxxxxx> <56424CB3.5090506@xxxxxxxxxxxxxxxx> <2108185319.9113269.1447193300260.JavaMail.zimbra@xxxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
On 11/11/15 09:08, Nathan Scott wrote:
...
It would be best to fail at build time if bits are missing that are expected.
Hmm, would configure options like --with-pmda-nginx=yes help here?  (causing
the build to fail IOW)  And explicitly listing the expectations in the distro
package builds.  Not sure if this really helps though, cos someone still has
to remember to add the configure options explicitly.  Hmm.

I don't think more configure scaffolding will help.

The crux of the matter is that "expected" is a moving feast. What I "expect" for the old SuSE version on an sgi ia64 machine is different to what someone else "expects" for rawhide or OS X or FreeBSD or ...

I think the status quo is probably about the best we can do with the available workers, provided we're vigilante for cases where "expected" changes or is in someway unsatisfactory.

<Prev in Thread] Current Thread [Next in Thread>