Re: libtool module output
Adriaan de Groot <adridg-FlD2LfDziEhmR6Xm/[email protected]>
| Newsgroups | gmane.comp.tools.aap.devel |
|---|---|
| Message-ID | <[email protected]> |
On Tuesday 14 October 2003 14:20, you wrote:
> Adriaan de Groot wrote:
> > attached one-liner patch stops aap from printing a cryptic -- bad
> > version -- message when there is a system-wide installed libtool
> > that's an old version (as in the case of freebsd ports).
>
> So you don't want to see the message on the terminal. But it would
> still be useful to know why Aap rejected this libtool.
The issue here is that Aap rejects one libtool but accepts another - for which
it doesn't produce a positive message. This can lead to weird situations
like:
$ aap
libtool - bad version
$
so is that a fatal error, or did Aap just complain and have nothing to build?
For this particular case, I think Aap should either:
1) complain about old versions in a sensible fashion and make a positive
statement when it gets a good version _or_
2) not complain or make positive comments, except maybe in the log
> Should we add a ":log" command, that works like ":print" but only writes
> the message in AAPDIR/log? I think that's a good idea.
Can't you use @msg_extra(_("Stuff")) for the same purpose? I think :log would
mostly be useful in modules, where you can expect a little Puython trickery.
--
pub 1024D/FEA2A3FE 2002-06-18 Adriaan de Groot <[email protected]>
If the door is ajar, can we fill it with door-jamb?
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php