[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: C++ libtool build error?

From: Bruno Haible
Subject: Re: C++ libtool build error?
Date: Sat, 13 Mar 2010 21:38:30 +0100
User-agent: KMail/1.9.9

Hi Jim,

> Rather than lumping them all into one "-extratests" category
> that is tied to the module file name, have you considered
> adding new module attributes?
> Then, we could give any module one or more attributes,
> and eventually exclude based on those attributes.
> For example, if a package maintainer wants to avoid C++ tests,
> they could do that without unnecessarily excluding long-running
> ones as well.

So, gnulib-tool would have command-line options
  --with[out]-unportable-tests     [for tests that fail on some platforms,
                                    e.g. flock, unlink, poll]

Sounds very reasonable to me.

IMO the default for --import and --update should be that these
tests are all turned off by default. For --create-testdir the
default has to be the same, otherwise people will be too confused.
Therefore a new option --with-all-tests will be required, for
the normal use of --create-testdir.

> And when this year's long-running test no longer 
> deserves its title in 2013, we won't have to change its name
> to put it back in the set of tests everyone runs by default.

Yes, simply removing the attribute "long-running" will do it.

I like your idea.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]