Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site pyuxt.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!gamma!pyuxww!pyuxt!marcus
From: marcus@pyuxt.UUCP (M. G. Hand)
Newsgroups: net.unix-wizards
Subject: Re: how can I tell when my shared text file is in use?
Message-ID: <107@pyuxt.UUCP>
Date: Thu, 10-May-84 22:56:52 EDT
Article-I.D.: pyuxt.107
Posted: Thu May 10 22:56:52 1984
Date-Received: Sat, 12-May-84 09:47:29 EDT
References: <462@burl.UUCP>
Organization: Bell Communications Research, Piscataway N.J.
Lines: 18

The method i have used (successfully) in the past tackles the problem in another
way.  Firstly you arrange your source and binary so that you execute an
*installed* version: that leaves you free to remake the binary in the source
directory. Then, when it comes to installing the program you use a make line
which effectively does this series of operations:

	rm -f $(INSD)/n$(PRODUCT)
	cp $(PRODUCT) $(INSD)/n$(PRODUCT)
	cd $(INSD); mv $(PRODUCT) o$(PRODUCT); mv n$(PRODUCT) $(PRODUCT); \
		rm -f o$(PRODUCT)

I say "effectively" because i would use a command macro called, eg $(INSCMD) to
hide the dirty work.

This results in users gradually swapping over to the new version as they
re-invoke the command.

		Marcus G Hand (pyuxt!marcus)