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

Feature request: The gemset path should be allowed to be arbitray #110

Open
573 opened this issue Sep 25, 2023 · 0 comments
Open

Feature request: The gemset path should be allowed to be arbitray #110

573 opened this issue Sep 25, 2023 · 0 comments

Comments

@573
Copy link

573 commented Sep 25, 2023

The gemset attribute of bundlerEnv should be allowed to point to an arbitrary path.

Incomplete working example using flakes:

cat flake/builders/mkDevenvRuby.nix
{ system, rootPath, pkgsFor, inputs, name, args, ... }:

let
  pkgs = pkgsFor.${system};

        ruby = inputs.nixpkgs-ruby.lib.packageFromRubyVersionFile {
          file = "${rootPath}/home/misc/.ruby-version";
          inherit system;
        };

        gems = pkgs.bundlerEnv {
          name = "gemset";
          inherit ruby;
          gemfile = "${rootPath}/home/misc/Gemfile";
          lockfile = "${rootPath}/home/misc/Gemfile.lock";
      # TODO Find out, why moving the generated gemset.nix to some other folder does not work
          gemset = "${rootPath}/flake/builders/gemset.nix";
          groups = [ "default" "production" "development" "test" ];
        };
      in
          pkgs.mkShell {
            buildInputs = [
              gems
              ruby
              pkgs.bundix
            ];
          }

When using "gemset = ${rootPath}/home/misc/gemset.nix"; instead this expression currently gives me:

 error: The option `gmail-britta' does not exist. Definition values:
       - In `/nix/store/z5l6xz6cpi8lcx1sjisaqvlav9rf784s-source/home/misc/gemset.nix':
           {
             dependencies = [
               "haml"
             ];
             groups = [
           ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant