[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference smurf::buildhelp

Title:USG buildhelp questions/answers
Moderator:SMURF::FILTER
Created:Mon Apr 26 1993
Last Modified:Mon Jan 20 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2763
Total number of notes:5802

1663.0. "the file didn t go away" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Fri Aug 11 1995 15:37

Date Of Receipt: 	 9-AUG-1995 11:07:01.58
From: 	SMURF::ALPHA::"[email protected]" "09-Aug-1995 1105"
To: 	[email protected]
CC: 	
Subj: 	the file didn't go away

Hi,

Yesterday I asked for help in getting rid of a ",v" file that was left
behind when I did a bcreate followed by a bcreate -undo.  I was told that
it would be automatically cleaned up overnight.  This hasn't happened
and the ,v file is still there:

1.226 marvin:ftw> bcreate startdhcp

[ ./sbin/init.d/startdhcp ]
[ source control information already exists in file: 
"./sbin/init.d/startdhcp,v" ]

BTW the reason why I did a bcreate followed by an undo is because I couldn't
figure out how to get bcreate to grok the fact that I want this to be a shell
script (and, to give me the appropriate header for that.)  Near as I can
tell if I have a file in the current directory that has the same name as
what I want to "bcreate" then bcreate will sniff this file and "do the right
thing".  Is this true?

Please remove the ,v file.


	-- Farrell

	-- Farrell


T.RTitleUserPersonal
Name
DateLines
1663.1Re: the file didn t go awayAOSG::FILTERAutomatic Posting Software - mail to flume::puckFri Aug 11 1995 15:4463
Date Of Receipt: 	 9-AUG-1995 11:42:41.64
From: 	SMURF::FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE  09-Aug-1995 1141"
To: 	[email protected]
CC: 	odehelp@DEC:.zko.flume
Subj: 	Re: the file didn't go away

Farrell, the clean-up happens different nights for different pools
(it also does a consistency check which takes a long time):
	Mon,Thu: os
	Tue,Fri: x11
	Wed,Sat: cde

You can use bcs -c to change the comment leader, after the file's been
created eg:
	bcs -c"# " foo
        bcs -c" * " bar
or the -c can be used in bcreate, or if you try to bco an get caught by
the menu, you can use the 'leader' option.

After bcs -c, you can then pull in the appropriate header to match from 
/usr/sde/osf1/headers/header.<ext>

You can resume working with the file by just doing a new bco, after the
bcs -u -o file.

bcreate isn't quite clever enough - if the file exists it'll set the comment
leader based on the extension, but using an rcs built-in list rather than
the headers directory.

I've removed the file anyway, just so you can get a clean start.

bcreate -c"# " startdhcp   will do what you wanted, then manually pull
in the appriate /usr/sde/osf1/headers/header.*sh file at the top. 

-josh

> Hi,
> 
> Yesterday I asked for help in getting rid of a ",v" file that was left
> behind when I did a bcreate followed by a bcreate -undo.  I was told that
> it would be automatically cleaned up overnight.  This hasn't happened
> and the ,v file is still there:
> 
> 1.226 marvin:ftw> bcreate startdhcp
> 
> [ ./sbin/init.d/startdhcp ]
> [ source control information already exists in file: 
> "./sbin/init.d/startdhcp,v" ]
> 
> BTW the reason why I did a bcreate followed by an undo is because I couldn't
> figure out how to get bcreate to grok the fact that I want this to be a shell
> script (and, to give me the appropriate header for that.)  Near as I can
> tell if I have a file in the current directory that has the same name as
> what I want to "bcreate" then bcreate will sniff this file and "do the right
> thing".  Is this true?
> 
> Please remove the ,v file.
> 
> 	-- Farrell