-
-
Notifications
You must be signed in to change notification settings - Fork 15k
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
tectonic, tectonic-unwrapped, texpresso: fix build & clean up #384706
base: master
Are you sure you want to change the base?
Conversation
I'm working on that. |
The previous implementation (overriding `buildRustPackage`) breaks downstream `buildRustPackage.overrides` in subtle ways. It's thus better to use `.overrideAttrs` explicitly and reconstruct `cargoDeps` when needed. This commit should cause no rebuild, but the underlying change is necessary for an upcoming patch on tectonic itself.
I rewrote parts of the P.S. I will postpone the re-format of texpresso/tectonic as it will obscure the patch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So is this ready? Or not well tested? Can we mark it as ready?
I haven't tested the build yet (only tested eval); but if it builds fine (and |
Testing it now with nixpkgs-review. |
|
Also tested the |
There are a few additional commits I'd like to push, and I'll fix the nixfmt CI reported issue in a few minutes. |
Move src closer to version attribute, so diffs of version bumps will be smaller and easier to read, and a version attribute changing without a hash changing will be more apparent, in case that happens.
I think it's good to go! Do we need to ping texpresso's maintainers? Or maybe we merge first since it's fixing broken builds? |
I wonder why CI hasn't pinged them already - there are many commits here prefixed with |
Let's give him say a day. Some of the changes here are somewhat stylistic and perhaps debatable. |
It seems to me that the new github "nix-owners" bot is less reliable than the previous ofborg one. I have seen many cases recently that a maintainer is not automatically pinged... I have no idea why. In any case, I have also tested .tex compile on an aarch64-darwin and all good. |
I suspect that it's due to the draft state that was modified during commits pushed, but I won't put an effort to verify & debug this. |
|
Supersedes:
clangStdenv
See #384610 for context.
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.