i can work with this
so plan is to update maintainer/maint.mk:
* web-manual will insert a link to the full versioned index in the index.html
that gendocs.sh produces
* i'm assuming that we don't want to modify lib/gendocs_template since it's
synced with upstream gnulib
* web-manual-update will also rsync a copy of the manual to manual/<version>/
* web-manual-update will update the full versioned index to include <version>so the default manual/ landing page & manual will be unchanged from today other than having a link to the full versioned index then i can manually backfill older versions, add the initial full versioned index page, and link it from the current index.html which leaves the last bikeshed: what form to use for the full versioned page. if we have it link to each version's landing page, that might side step some debate. so it'd look like: <h2>GNU Automake Manuals</h2> <ul> <li><a href="1.16">GNU Automake 1.16</a></li> <li><a href="1.15.1">GNU Automake 1.15.1</a></li> <li><a href="1.15">GNU Automake 1.15</a></li> <li><a href="1.14.1">GNU Automake 1.14.1</a></li> ... </ul> if we wanted to get fancy we could inline common targets like HTML/PDF, but i'd be fine leaving it at an <ul> too. not exactly a common flow. <table> <tr> <th>Date</th> <th>Version</th> <th>HTML</th> <th>PDF</th> </tr> <tr> <td>Feb 2018</td> <td><a href="1.16">GNU Automake 1.16</a></td> <td><a href="1.16/automake.html">HTML</a></td> <td><a href="1.16/automake.pdf">PDF</a></td> </tr> ... -mike
signature.asc
Description: PGP signature
