On Tue, Jan 21, 2003 at 08:51:09AM -0800, Bruce A. Mah wrote:
The problem with the installation instructions is that the content is
scattered throughout several files and there is not any single
$FreeBSD$ tag you (or anybody) can use to give the latest revision date
for the document as a whole.
I hate it when you are right and have to ditch one of my half-cooked ideas
into the trashcan. Obviously, adding a visible $FreeBSD$ tag to each
file would look... strange.
I'm only right because I've run into this problem too. Also I
*designed* this mess. :-)
I *think* you can do this for the installation guide as well, and I
wouldn't object to somebody doing this if it can be made to work.
Why do I get the nasty feeling that this will be more complicated
than just doing a gigantic cat * > newfile.sgml?
I haven't really looked at this (ENOTIME) but it might actually *be*
It can't be done for the hardware notes, because there are some MD
Which mean that even if I manage to add a usefull publication date to
the installation instructions, I am still short of my target of having
a way to automatically identify the parts of the rendered release notes
that are out of date... short of building them and running diff, that
But you'd be closer. A lot of these problems (believe it or not) would
go away if we had better conditionals for building text. Heck, cpp(1)
would do better than what I'm using now. :-(