1. A minor bug, the hyperlink for "sqlite:" pointed to
mysql_table.5.html:
--- postfix-2.8-20100618/html/BAD-SQLITE_README.html 2010-06-18
13:15:23.000000000 -0000
+++ postfix-2.8-20100618/html/SQLITE_README.html 2010-06-27
15:52:16.992251367 -0000
@@ -54,7 +54,7 @@
<blockquote>
<pre>
-<a href="postconf.5.html#alias_maps">alias_maps</a> = <a
href="mysql_table.5.html">sqlite</a>:/etc/postfix/sqlite-aliases.cf
+<a href="postconf.5.html#alias_maps">alias_maps</a> = <a
href="sqlite_table.5.html">sqlite</a>:/etc/postfix/sqlite-aliases.cf
</pre>
</blockquote>
2. SQLITE_README does not mention version 2.8 availability.
sqlite_table(5) does. I think the README should, too.
3. sqlite_table(5) mentions the deprecated query syntax. I guess
that's loaded from shared code with older SQL map types? Seems to me
that there's no need to support that in sqlite_table, unless of
course it's more work to NOT support it.
4. This has happened to me before, and I think I even brought it up
here: "make upgrade" goes through my $html_directory, but I don't get
the new goodies I was after.
This time I noticed on two systems that I did not get the sqlite
documents upon upgrade from earlier (February 13) snapshots. On
further inspection I saw that index.html was not updated, and
SOHO_README.html was also missing.
Disclosure: one of these was make upgrade'ed lots of times since
2.5.1 in '08. (The other was originally a 2.7 snapshot.)
Also: it seems that SQLITE_README made it to $readme_directory, and
man5/sqlite_table.5 is there, but SOHO_README is not.
Do I need to use something like rsync in addition to make upgrade?
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
