Inline rubygems patch to fix sha mismatch

[will]

It's strange to me that the nix sha could change for the same patch, but it's small enough I figure it'd be easier to inline it to the repo rather than pull it down to make sure it doesn't happen again

Fixes #11

[thecatwasnot]

I found it strange too. I forked and changed the sha to test, no further issues that way but this seems better. Thanks!

[bobvanderlinden]

I personally do like having the patch files referenced by fetching them from an url. It gives a bit more context where these patches come from. I'd like to avoid having a large number of patch files in the repo if they were sourced/copied from somewhere else.

#23 made quite a few changes to the project. It is now fetching raw patch files from the nixpkgs repository. I'm still not 100% sure why the hashes have changed, but I suspect it has something to do with fetchpatch using various tools internally that might have been upgraded and now give an output in a backwards incompatible way. I didn't notice the change in hash, as it was already built locally unfortunately.

Would it then be better to use fetchurl instead of fetchpatch?