<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0">
</HEAD>
<BODY>
On Thu, 2010-10-28 at 21:55 +0200, Cyril Brulebois wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
Gaetan Nadon <<A HREF="mailto:memsize@videotron.ca">memsize@videotron.ca</A>> (11/10/2010):
> I don't mind giving more flexibility, but it will generate a
> "defaults" war.
Talking about flexibility, I've got two remarks about fop:
- It uses format autodetection by default, using papersize and
locales settings. People building packages for distributions may
like the concept of build reproducibility and may want to build
stuff independently of the environment. It'd be nice to be able to
pass --noautosize without having to patch all specs/Makefile.am
files in Xorg packages.
</PRE>
</BLOCKQUOTE>
One solution comes to mind. An Autoconf aware variable, say XMLTO_OPTS<BR>
<BR>
The usage option would look like:
<BLOCKQUOTE>
<PRE>
Some influential environment variables:
CC C compiler command
CFLAGS C compiler flags
LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
nonstandard directory <lib dir>
LIBS libraries to pass to the linker, e.g. -l<library>
CPPFLAGS C/C++/Objective C preprocessor flags, e.g. -I<include dir> if
you have headers in a nonstandard directory <include dir>
CPP C preprocessor
PKG_CONFIG path to pkg-config utility
XMLTO Path to xmlto command
XMLTO_OPTS Options for xmlto command
FOP Path to fop command
[...]
</PRE>
</BLOCKQUOTE>
The makefile would be changed to:<BR>
<BR>
<BLOCKQUOTE>
<PRE>
XMLTO_FLAGS = -m $(XSL_STYLESHEET) $(XMLTO_OPTS)
</PRE>
</BLOCKQUOTE>
<BR>
The command line invocation would be:<BR>
<BR>
./configure XMLTO_OPTS="--noautosize"<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
- Fop is very chatty, and may clutter the build log with messages
which aren't going to be read except by a few developers (I'm not
even sure?). It'd be nice to be able to tell it to be less
chatty. Since no option seems to exist for that matter, I guess
it'll still be nice to be able to redirect its std{out,err} to
/dev/null…
</PRE>
</BLOCKQUOTE>
A bit more tricky. Using Automake 1.11, you can the "silent rules" for free.<BR>
All you see is:
<BLOCKQUOTE>
<PRE>
GEN libXaw.txt
</PRE>
</BLOCKQUOTE>
for the text conversion. For the pdf version, you see a bunch of warnings.<BR>
The perfect solutions would be to fix the code so no warning is emitted.<BR>
Suppressing the output means the build log will not show errors either.<BR>
You can always pass >/dev/null 2>&1 in XMLTO_OPTS<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
What do you think?
(I've been playing around with libXaw for now, but I guess the same
applies to all Xorg packages with reworked documentation handling.)
</PRE>
</BLOCKQUOTE>
Now that the are distributed with the package they document, it make sense that<BR>
it creates new requirements.<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
Mraw,
KiBi.
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>