Make incompatible with source control?

[Ken Arnold%UCB]

>The underlying cause of the problem is SCCS's peculiar notion of the
>meaning of the "w" bit. It is not just "make" that doesn't understand
>this idea. Almost all other utilities (such as "cp" and "rm") believe
>that you will turn off the "w" bit if you want a file to be treated
>with extra care. SCCS believes exactly the opposite. For example, you
>have gotten several files in a directory, some with -e and some
>without.   You now accidentally do an "rm *".  What happens? The
>files you have spent hours editing are removed, but the ones you can
>easily recreate are not.
>
>Jerry Schwarz
>Bell Labs
>Summit, N.J.

I think we have a mistaken idea here.  The 'w' bit controls whether
the file is writeable.  It does NOT mean "take extra care with this
file".  The behavior you note is consistent with this meaning.

	rm	If you can't write a file, should you really be
		deleting it entirely?

	sccs, rcs
		If you don't have a file checked out for editing,
		you shouldn't be modifying the contents.  If you
		check out a file to edit it, you damn well better
		be able to write on it.

You are mistaking "rm" and "mv"'s behavior as "This file is precious".
It is really just saying "Removing this file seems strange, are you sure?"
'w' == write access.  If you want something like this, you'll have to
add a "precious" bit.

		Ken Arnold