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

Multiple overrides for the same package #1737

Open
TyberiusPrime opened this issue Jul 15, 2024 · 2 comments
Open

Multiple overrides for the same package #1737

TyberiusPrime opened this issue Jul 15, 2024 · 2 comments

Comments

@TyberiusPrime
Copy link
Contributor

For I have the equivalent of

 (final: prev: {
    "pysam" = prev."pysam".overridePythonAttrs (
      old: {
        buildInputs = (builtins.trace "two" (old.builtInputs or [])) ++ [pkgs.bzip2];
        nativeBuildInputs = builtins.trace "two-b" (old.nativeBuildInputs or []);
      }
    );
  })
  (final: prev: {
    "pysam" = prev."pysam".overridePythonAttrs (
      old: {
        buildInputs = (builtins.trace "one" (old.builtInputs or [])) ++ [pkgs.zlib];
      }
    );
  })

in my overrides, and find that it's not toking the first one.
The traces read
'one'
'two-b'

and I'd like to know if I'm holding it wrong or if this is how it's supposed to work?

@heimalne
Copy link

heimalne commented Jul 17, 2024

The trace seems weird indeed regarding the evaluation order. In order to evaluate the final pysam value we use the latest/last entry (prints "one"), but this dependes on the previous/old on, which when evaluated should print "two".

@TyberiusPrime
Copy link
Contributor Author

Thanks @heimalne that's how I understood 'a list of overlays' should work, the 'old' in the 2nd one should be what the first one produced.

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

2 participants