Updating source code manually

[Robert Huff]

Sergey Zaharchenko writes:

>  When a file is open by a process, even if you unlink it and replace it
>  with another one, the original file will stay on disk until the last
>  file handle referencing it is closed.

	Yes.

>  I assume that holds true for libraries too.

	I don't ... but I must also allow as I'm talking at the border
between understanding, informed speculation, and outright guesswork.

>  So, EXISTING processes aren't screwed. But, when a NEW
>  process is created, it references the NEW shared library, and if their
>  ABI's don't match --- BOOM!:) That was just a correction.
>  
>  I was under the impression that the OP already had KDE (and thus all
>  `father' ports) installed and up-to-date, and only wanted to patch a
>  file.

	I don't remember whether he said "up to date"; if so, then  my
worries are moot.
	I run a few KDE apps, but very little of the larger
environment,  Every time I have upgraded even one of those apps it
has provoked a long, tortuous (and not always sucessful) session of
upgrading other ports.


>  Please read more carefully. I mentioned '-w'.

	Mea culpa.  Sorry.


				Robert Huff