Enlarge description of gem pristine #388
Description
I updated my system and started getting warnings of the kind "Nokogiri was built against LibXML version 2.7.8, but has dynamically loaded 2.9.0". After some googling I found someone recommended using gem pristine to fix this. I looked up the documentation for this command and couldn't see at all how "Restores installed gems to pristine condition from files located in the gem cache" would help, as files in the gem cache would still be the same because I didn't make any changes. I read the detailed decription too but did not see how that would affect my case since, again, I did not modify the gem.
In the end I tried the command and to my astonishment it recompiled the native extension, indeed fixing the problem. Since people upgrade their system all the time, would it make sense to document how gem pristine helps updating gems with native extensions after a system update? "pristine" is a bit of a misnomer in this case, so this command is not an intuitive candidate for a solution.