Be warned that using the svn revision as minor as the advantage of auto-bumping, but also a drawback: I doesn't work well if you move (=migrate) or copy(=hard-embed) the file into another SVN repository.
As for the change:
1) define the svn:keywords property on the file (see svn doc)
svn propset svn:keywords Revision myLib-1.0.lua
2) use the keywords in the myLib-1.0.lua:
local MAJOR = "myLib-1.0"
local MINOR = tonumber(string.match("$Revision: 0 $", "%d+"))
local lib = LibStub:NewLibrary(MAJOR, MINOR)
The "$Revision: 0 $" string will automatically be replaced by something like "$Revision: 144 $" on checkout and the string.match catchs the number. Alternatively, some people prefer using string.sub:
local MINOR = tonumber(string.sub("$Revision: 0 $", 12, -3))
The answer lies in the code : LRC uses the Blizzard events to monitor player's casting only. It expects other group members to have LRC too and thus it ignores all spellcast events from other characters. It would be possible to monitor other res but there is no way to know the target for sure, which is why LRC exists in the first place.
Back to your example, if a priest with LRC and a paladin without IRC were both ressing the same target, a modified LRC could tell that both are ressing someone but not the target of the paladin.