Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove yarn2nix, see #20637 #58424

Merged
merged 1 commit into from Mar 27, 2019
Merged

Remove yarn2nix, see #20637 #58424

merged 1 commit into from Mar 27, 2019

Conversation

domenkozar
Copy link
Member

@domenkozar domenkozar commented Mar 27, 2019

#20637 cc @moretea

Uses outdated yarn2nix version, node 8.X, etc.

yarn2nix = callPackage ../development/tools/yarn2nix { };
inherit (yarn2nix) mkYarnPackage;

yarn2nix = throw "Use upstream https://github.com/moretea/yarn2nix";
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for yan2nix binary, why not using

  yarn2nix = (callPackage (fetchFromGitHub {
    owner = "moretea";
    repo = "yarn2nix";
    rev = "master";
    sha256 = "1f83cr9qgk95g3571ps644rvgfzv2i4i7532q8pg405s4q5ada3h";
  }) {}).yarn2nix;

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. This doesn't lock down the revision, so this will break as soon as something new is pushed to Yarn2nix's master.
  2. Nixpkgs doesn't allow importing from the output of derivations (such as fetches), since Hydra doesn't support that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants