89023c38fc
I made a mistake merge. Reverting it inc778945806undid the state on master, but now I realize it crippled the git merge mechanism. As the merge contained a mix of commits from `master..staging-next` and other commits from `staging-next..staging`, it got the `staging-next` branch into a state that was difficult to recover. I reconstructed the "desired" state of staging-next tree by: - checking out the last commit of the problematic range:4effe769e2- `git rebase -i --preserve-merges a8a018ddc0` - dropping the mistaken merge commit and its revert from that range (while keeping reapplication from4effe769e2) - merging the last unaffected staging-next commit (803ca85c20) - fortunately no other commits have been pushed to staging-next yet - applying a diff on staging-next to get it into that state
36 lines
946 B
Nix
36 lines
946 B
Nix
{ stdenv, lib, fetchurl, fetchpatch }:
|
|
|
|
stdenv.mkDerivation rec {
|
|
name = "rubygems";
|
|
version = "3.1.3";
|
|
|
|
src = fetchurl {
|
|
url = "https://rubygems.org/rubygems/rubygems-${version}.tgz";
|
|
sha256 = "181wjclxnq5lrwnr53famy9pg8911hi9w2v0vy7dqgjqnc4iy1hp";
|
|
};
|
|
|
|
patches = [
|
|
./0001-add-post-extract-hook.patch
|
|
./0002-binaries-with-env-shebang.patch
|
|
./0003-gem-install-default-to-user.patch
|
|
|
|
(fetchpatch {
|
|
url = "https://github.com/rubygems/rubygems/commit/0af4d2d369ff580ef54839ec15a8c7ec419978cb.patch";
|
|
sha256 = "13gyfxn4rmxq1dbxq5rzphnhagn8n8kpp8lb9h6h4s9d4zaklax9";
|
|
})
|
|
];
|
|
|
|
installPhase = ''
|
|
runHook preInstall
|
|
cp -r . $out
|
|
runHook postInstall
|
|
'';
|
|
|
|
meta = with lib; {
|
|
description = "Package management framework for Ruby";
|
|
homepage = "https://rubygems.org/";
|
|
license = with licenses; [ mit /* or */ ruby ];
|
|
maintainers = with maintainers; [ qyliss zimbatm ];
|
|
};
|
|
}
|