On Wed, 21 Feb 2001 16:52:03 +0100, Richard Foley <[EMAIL PROTECTED]> wrote:
> "H.Merijn Brand" wrote:
> >
> > > >
> > > > Here I mean that Configure is unable to proceed with the given configuration,
> > > > e.g. 'Configure -Dusethreads' on a system that does /not/ support threads or
> > > > 'Configure -Duse64bitall' on an OS that does not support 64 bit operations.
> > > >
> > >
> > > Sounds like a failure to me (being a layman :), I would have thought
> > > Configure should step around it or fail? Though you could always stick
> > > in a new status?
> > >
> > > crippled|injured|...
> >
> > incapable
> >
> > > BTW that's another category is it, distinct from install?
> > >
> > > configure
> >
> > But than we'd not be able to group the dailybuild reports, in which these
> > configuration failures will pop-up on a daily basis.
> >
> > I don't think that if we're going on on this road, *any* of the smokers would
> > be interested in ack's, wouldn't we?
> >
> > category=configure
> > status=incapable
> > severity=low
> > ack=daily
> >
> ack=no
I know, but it was a suggestion to use the category for what it's meant for and
/still/ be able to see it was from daily.
--
H.Merijn Brand Amsterdam Perl Mongers (http://www.amsterdam.pm.org/)
using perl-5.005.03, 5.6.0, 5.6.1, 5.7.1 & 623 on HP-UX 10.20 & 11.00, AIX 4.2
AIX 4.3, WinNT 4, Win2K pro & WinCE 2.11 often with Tk800.022 &/| DBD-Unify
ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/H/HM/HMBRAND/
