Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Jan 2003 06:32:35 -0800
From:      "Bruce A. Mah" <bmah@FreeBSD.ORG>
To:        Udo Erdelhoff <ue@nathan.ruhr.de>
Cc:        freebsd-doc@FreeBSD.ORG
Subject:   Re: Adding a publication date to the installation instructions 
Message-ID:  <200301221432.h0MEWZC7013773@intruder.bmah.org>
In-Reply-To: <20030121191802.GE173@nathan.ruhr.de> 
References:  <20030120205441.GC173@nathan.ruhr.de> <200301211651.h0LGp9nS001708@intruder.bmah.org> <20030121191802.GE173@nathan.ruhr.de>

next in thread | previous in thread | raw e-mail | index | archive | help
--==_Exmh_-926300294P
Content-Type: text/plain; charset=us-ascii

If memory serves me right, Udo Erdelhoff wrote:
> Bruce,
> 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*
that easy.

> > It can't be done for the hardware notes, because there are some MD
> > files.
> 
> 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
> is.

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.  :-(

Bruce.



--==_Exmh_-926300294P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.0 (FreeBSD)
Comment: Exmh version 2.5+ 20020506

iD8DBQE+LquD2MoxcVugUsMRAk9WAKCkeWM7FbEsr/Jext8n0oL8vdBuZACdGldt
RSiOu0GkwpkfRwUg8wXdM3U=
=P/ui
-----END PGP SIGNATURE-----

--==_Exmh_-926300294P--

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-doc" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200301221432.h0MEWZC7013773>