Conference smurf::buildhelp

Date Of Receipt: 	 3-JUN-1993 09:18:21.77
From: 	FLUME::"[email protected]" "Grant Van Dyck"
To: 	[email protected]
CC: 	[email protected], [email protected], [email protected]
Subj: 	Re: defuncting files

Yes Mary, you win ODE-Jeopardy for today, and Brett, we have a nice 
Toaster-Oven for you as a consolation prize.  :-)

The steps you outline are correct with the addition of the actual
bsubmit step which removes the file from the submit tree, adds it to
the defunct list and defuncts the file on the Public branch.

The RCS file however, lives on forever; it's simply marked as defunct
from that point on.  If it was created during a previous release or
baselevel, it's still a real file for that release and must be accessible.
If at some future point you wish to use this file again, then you
should contact reng to un-defunct the file.

This is different that the case where you inadvertently create the wrong
file, or create it and then change your mind about using it. In those
cases, the file has never been submitted and we can simply remove it.


	-Grant

| 
| Hi ode-ers,
| 
| When you no longer are using a file in the source tree I was under the impres
sion
| that you do the following:
| 	1) bco filename
| 	   bci -defunct filename
| 	2) in your submit request add it to the defunct list if applicable.
| 	3) in your submit request add the filename to the list to be submitted.
| 
| In some mail between brett and a few of us, Brett mentioned:
| 
| > Last, if you realy want to do this you should send mail to ODE help
| > and ask them about defuncting files. Because when everything is done,
| > the ODE elfs must do somthing to the underlieing rcs files.
| 
| 
| Can you please help clarify the correct steps?
| 
| thanks,
| Mary
| 

Date Of Receipt: 	14-JUN-1993 14:26:21.08
From: 	WASTED::jmf "Joshua M. Friedman ULTRIX SDE  14-Jun-1993 1427"
To: 	[email protected]
CC: 	[email protected], [email protected], [email protected],
	jmf@wasted:zko.dec
Subj: 	Re: defuncting files

Mary, did you ever get an answer to this?  ODE elfs are only required
to UNdefunct a file.  Defuncting is completely under the control of
the submittor.  This is for "real" defuncts.

If, however, in a shared sandbox, you have submitted a file, but no longer
want that file to come from the sharedsb, but want to "inherit it" again,
you can do one of two things: submit the file defunct (see above if the
file then needs to be used again), or, as shared sb admin, do a workon
to the sharedsb, and then do a "bcs -o" on the file.  This will remove it
from the shared sb and remove its branch.  You then should manually remove
it from the shared sb's SNAPSHOT file for bookkeeping.

-josh

--------
Return-Path: [email protected]
Received: by abyss.zk3.dec.com (5.65/DEC-USSG-ZK3-ULTRIX-09/27/91);
	id AA01024; Thu, 3 Jun 1993 08:59:55 -0400
Message-Id: <[email protected]>
To: [email protected]
Cc: [email protected], [email protected]
Subject: defuncting files
Date: Thu, 03 Jun 93 08:59:54 -0400
From: [email protected]
X-Mts: smtp


Hi ode-ers,

When you no longer are using a file in the source tree I was under the 
impression
that you do the following:
	1) bco filename
	   bci -defunct filename
	2) in your submit request add it to the defunct list if applicable.
	3) in your submit request add the filename to the list to be submitted.

In some mail between brett and a few of us, Brett mentioned:

> Last, if you realy want to do this you should send mail to ODE help
> and ask them about defuncting files. Because when everything is done,
> the ODE elfs must do somthing to the underlieing rcs files.


Can you please help clarify the correct steps?

thanks,
Mary

Date Of Receipt: 	19-OCT-1994 16:19:47.62
From: 	WASTED::dlong "David Long OSG  19-Oct-1994 1616"
To: 	odehelp@DEC:.zko.wasted
CC: 	
Subj: 	defuncting

When I defunct a file in my sandbox I am solicited for a log message.  Where is 
this message stored when I am done?

-dl

Date Of Receipt: 	19-OCT-1994 16:26:00.58
From: 	FLUME::jmcg "Jim McGinness"
To: 	dlong@DEC:.zko.flume
CC: 	odehelp@DEC:.zko.flume
Subj: 	Re:  defuncting

The message you provide goes into the log section of the RCS file.  It
should be visible to someone who does a "blog" on the file.  It goes
away if you outdate your changes; it would also get transfered to the
branch you bsubmit to later on if you don't outdate the changes.

Date Of Receipt: 	19-OCT-1994 16:34:00.36
From: 	WASTED::dlong "David Long OSG  19-Oct-1994 1631"
To: 	Jim McGinness <[email protected]>
CC: 	dlong@DEC:.zko.wasted, odehelp@DEC:.zko.wasted
Subj: 	Re: defuncting

OK.  blog was showing me someone elses log message until I used the -r option 
with the right revision number (which bstat refuses to disclose to me).

-dl

Date Of Receipt: 	19-OCT-1994 16:45:15.36
From: 	FLAMBE::jmf "Joshua M. Friedman OSF/UNIX SDE"
To: 	dlong@DEC:.zko.flambe, [email protected]
CC: 	odehelp@DEC:.zko.flambe
Subj: 	Re: defuncting

Actually there's a bug (I call it a bug) that bsubmit of something
that's been defuncted will put the message "file is defunct" in RCS
instead of the message used during the bci.  To override this, you
can use the <-m "comment ..."> with the bsubmit.

-josh

Date Of Receipt: 	27-APR-1995 14:24:35.80
From: 	SMURF::FLUME::daniele "Mike Daniele  27-Apr-1995 1423"
To: 	odeadmin@DEC:.zko.flume
CC: 	
Subj: 	defuncting files

I just (bco)ed then (bci -defunct)ed a bunch of files.

I can't seem to find any indication now that anything haappened.

My srequest has a bunch of lines like

[ ./usr/sbin/snmpd/v_udp.c ]
[ There is no branch revison for set Michael_Daniele_esnmp. ]

and bstat & blog don't show me anything that gives me a warm
fuzzy feeling that these files really will be defuncted.

Did I omit some other step?

Thanks,
Mike 

Date Of Receipt: 	28-APR-1995 08:31:33.23
From: 	SMURF::SEAN::davidson "D. Sean Davidson"
To: 	daniele odeadmin
CC: 	
Subj: 	Re:  defuncting files

When you submit these files they will be removed from the submit source tree.

Sean

Date Of Receipt: 	 5-NOV-1996 08:16:47.79
From: 	WASTED::beltz "James Beltz USG  05-Nov-1996 0813"
To: 	odehelp@DEC:.zko.wasted
CC: 	
Subj: 	defuncting files

Hi,
  I'm planning on defuncting several files as part of a steel project.  Do I
  need to do anything other than use 'bci -defunct' for these files and 
  indicate which ones have been defuncted on the srequest?  Who modifies
  the Makefiles?  Thanks.

  - Jim

Date Of Receipt: 	 5-NOV-1996 08:23:07.26
From: 	SEAN::davidson "D. Sean Davidson"
To: 	beltz odehelp
CC: 	
Subj: 	Re:  defuncting files

Jim,

You need to modify any Makefiles that used to do any processing with these
files.

Yes you just check them in defuncted 'bci -defunct' and when you do your
bsubmit the sources will be removed from the submit tree.

Your bstat lines in your srequest will indicate that these are being defuncted.

If any of these files ship on a kit you will need to enter those files in the
DEFUNCT inventory section of the submit request form.

Sean

Date Of Receipt: 	 5-NOV-1996 10:18:49.20
From: 	FLUME::mkm "Michael Martin USG"
To: 	[email protected] (beltz)
CC: 	odehelp@DEC:.zko.flume
Subj: 	Re: defuncting files

Jim,
  You need to change the Makefile so it will not attempt to build the files
that you have defuncted..In addition, you need to either change the 
files file (if using .mod) or the .mi and remove the files....
Mike Martin
> 
> Hi,
>   I'm planning on defuncting several files as part of a steel project.  Do I
>   need to do anything other than use 'bci -defunct' for these files and 
>   indicate which ones have been defuncted on the srequest?  Who modifies
>   the Makefiles?  Thanks.
> 
>   - Jim
>