John Levon wrote:
> This makes the sources diverge, it essentially means you're now the
> maintainer of qt.m4. Fine by me.
???
I've retired. I'm maintaining nowt. Anyway, this thread has gone on
way too long, so I'll shut up and bugger off.
--
Angus
On Wed, Nov 09, 2005 at 09:34:38PM +, Angus Leeming wrote:
> With your original, FATAL=0, code you'd get no other error message at all.
That's a configurable parameter, easy to merge.
> At least with Georg's addition to configure.ac, we get something
> reasonably descriptive at the end of th
John Levon wrote:
> On Wed, Nov 09, 2005 at 11:16:32AM +, Angus Leeming wrote:
>
>> Sorry, that's FUD. AC_MSG_ERROR (currently disabled) would print an
>> error message and abort. LYX_ERROR would not abort but would print an
>> error message at the end of configuration. In other words, it wou
On Wed, Nov 09, 2005 at 11:16:32AM +, Angus Leeming wrote:
> Sorry, that's FUD. AC_MSG_ERROR (currently disabled) would print an
> error message and abort. LYX_ERROR would not abort but would print an
> error message at the end of configuration. In other words, it would
> do exactly what the c
John Levon wrote:
> On Tue, Nov 08, 2005 at 07:38:23PM +, Angus Leeming wrote:
>> Let's turn your argument around: why not wrap LYX_ERROR on your
>> side?
>
> For the same reason that the C library doesn't have functions called
> apache_*() - generic code uses generic names.
Sorry, that's FU
On Tue, Nov 08, 2005 at 07:38:23PM +, Angus Leeming wrote:
> A coherent error message
eh?
> self explanatory and maintainable code in only one place?
You don't maintain AC_MSG_ERROR, the autoconf authors.
> Let's turn your argument around: why not wrap LYX_ERROR on your side?
For the same
John Levon wrote:
>> > I guess the question is whether John still uses qt.m4 in oprofile...
>>
>> Oh, c'mo guys! That's just feeble.
>
> Why is it feeble? It's no different to using a macro from one of the
> autoconf libraries. If there's no reason to fork, then don't. What does
> LYX_ERROR b
On Tue, Nov 08, 2005 at 02:56:19PM +, Angus Leeming wrote:
> > I guess the question is whether John still uses qt.m4 in oprofile...
>
> Oh, c'mo guys! That's just feeble.
Why is it feeble? It's no different to using a macro from one of the
autoconf libraries. If there's no reason to fork
Jean-Marc Lasgouttes wrote:
> Angus> Can someone explain the rationale for those LYX_ERROR
> messages Angus> in configure.ac if some Qt component is not found?
> Why aren't Angus> we using LYX_ERROR in qt.m4 as in the attached
> file?
>
> I guess the question is whether John still uses qt.m4 in op
Angus Leeming wrote:
> Can someone explain the rationale for those LYX_ERROR messages in
> configure.ac if some Qt component is not found? Why aren't we using
> LYX_ERROR in qt.m4 as in the attached file?
probably because of this comment in qt.m4:
dnl Please leave this alone. I use this
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Can someone explain the rationale for those LYX_ERROR messages
Angus> in configure.ac if some Qt component is not found? Why aren't
Angus> we using LYX_ERROR in qt.m4 as in the attached file?
I guess the question is whether John st
Can someone explain the rationale for those LYX_ERROR messages in
configure.ac if some Qt component is not found? Why aren't we using
LYX_ERROR in qt.m4 as in the attached file?
--
AngusIndex: config/qt.m4
===
RCS file: /usr/local/ly
12 matches
Mail list logo
