Conference smurf::buildhelp

2710.0. "Re: ode source macros question" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Wed Dec 04 1996 14:14

Date Of Receipt: 	 4-DEC-1996 14:06:14.15
From: 	FLUME::jmf "Joshua M. Friedman Digital UNIX"
To: 	[email protected]
CC: 	odehelp@DEC:.zko.flume
Subj: 	Re:  ode source macros question

Ernie, this is the kind of message good to send to odehelp; so I've copied
them on my reply here.

You can make the file a "no header" file, but still include RCS version
information, I think.  If you set the comment leader as follows:

	bcs -cNONE filename

	(rather than: bcs -c"! " filename)

Then ode won't expect any header at all, however it sill may expand the 
keywords.  If it doesn't, there's a way to set the file so it does (at the
end of an ode blog operation's header output, there's both a comment
leader entry and a keyword expansion entry, and both are reset when you
do the bcs -cNONE.

Give that a try and see how it works.  Do a bci and see if the "mini header"
now reflects the correct version for your private branch after the bci.

-josh


------------
From [email protected]  Tue Dec  3 14:43:52 1996
Delivery-Date: Tue, 03 Dec 96 14:43:57 -0500
To: [email protected]
Cc: [email protected]
Subject: ode source macros question
Date: Tue, 03 Dec 96 14:43:30 -0500
From: [email protected]
X-Mts: smtp

Hi,

I am creating a new file and I would like to have the following for
the first line in the file:

	! @(#)$RCSfile$ $Revision$ $Date$

The bci command generates the following error message:

bci: Header file ./usr/sbin/lpd/filters/pcf/generic_ansi.pcf malformed.

The base file was created using: bcreate -c"! " generic_ansi.pcf

After running a few tests I suspect bci wants:

	! @COPYRIGHT@
	! HISTORY
	! @(#)$RCSfile$ $Revision$ $Date$

Is there a way to get only the filename, revision, and date?

Ernie