<!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 Tue, 2010-11-23 at 13:24 -0500, Trevor Woerner wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<TT><FONT COLOR="#1a1a1a">That sounds great to me, I can get started on that. Maybe we should</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">leave off the "build" part since we're both building and installing?</FONT></TT><BR>
<BR>
</BLOCKQUOTE>
I only spent 0.538 ms thinking about the option name.<BR>
<BLOCKQUOTE TYPE=CITE>
<TT><FONT COLOR="#1a1a1a">The only question I have remaining is: if I user invokes build.sh with</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">this new option, what are they expecting to see built and installed?</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">man pages? specs? developer documentation? all of the above? I'm</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">guessing you just want the specs and developer documentation, but I</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">just wanted to be double-check.</FONT></TT><BR>
<BR>
</BLOCKQUOTE>
Anything covered by --enable-docs --enable-devel-docs and --enable-specs<BR>
as outlined in the wiki table. No man pages.<BR>
<BR>
Disregard the server "legacy" enable-builddocs which will be removed eventually.<BR>
<BR>
Conversely, it would be nice to have "don't build docs" option.<BR>
This would be very appreciated by many. Just keep that in mind when designing the code.<BR>
<BR>
Perhaps --docs-only and --no-docs
</BODY>
</HTML>