Daniel Stenberg wrote:
>
> If so, how on earth can we cram that into the page without making
> everything a huge mess?

I would put a "Legend" (h2) subtitle before the info at the end of the
table, and an additional line saying something like "See the legend for
package options" that links to it from before the table.

The table could have an extra column that reflects what options and
tools have been used to build the package. It could use the same cryptic
acronyms used for the package file names, possibly adorned with specific
colors or typeface. Any extra library requirement would then be listed
along with other explanations in the relevant legend entry.

E.g. instead of this snippet
    Win32 metalink 7.16.4 libcurl SSL enabled Daniel Stenberg 448 KB
    Win32 2000/XP metalink 7.16.4 binary SSL disabled Daniel Stenberg 220 KB

we'd have
    Win32 metalink 7.16.4 libcurl SSL enabled Daniel Stenberg 448 KB
    Win32 metalink 7.16.4 binary SSL disabled Daniel Stenberg 220 KB sspi

and in the legend
    sspi whether to enable SSPI support (win32 builds only)
Received on 2007-07-16