Re: libtool module output
Bram Moolenaar <[email protected]>
| Newsgroups | gmane.comp.tools.aap.devel |
|---|---|
| Message-ID | <[email protected]> |
Adriaan de Groot wrote:
> 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
Yes, that's exactly where a log message is appropriate. Suppose the
recipe selects a libtool with a strange path, and the user wants to know
why Aap didn't use a more obvious one. Then you can see in the log file
why it was rejected. To make it even more clear what happens, you could
make it "libtool - bad version; looking for another one".
> > 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.
You could call msg_extra(), but that's very low-level. The nice thing
about ":log" is that it works like ":print", variables in the argument
are expanded.
I try to provide Aap commands for the most often used things. Only
advanced functionality may require using Python.
--
hundred-and-one symptoms of being an internet addict:
229. You spend so much time thinking what to add on this list.
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// Creator of Vim - Vi IMproved -- http://www.Vim.org \\\
\\\ Project leader for A-A-P -- http://www.A-A-P.org ///
\\\ Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html ///
-------------------------------------------------------
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