We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Just the obvious example: We use buildInputs everywhere instead of distinguishing it from nativeBuildInputs.
buildInputs
nativeBuildInputs
I don't currently know if our racket package derivations are platform-specific or not. Are *.zo files platform-specific?
*.zo
Not a high priority, but if we're lucky it might enable hydra to make some of the packages for darwin without involving darwin.
The text was updated successfully, but these errors were encountered:
Yeah I'm looking for a second hand mac mini. We can pick this up once that's on the way
Sorry, something went wrong.
This is more about the conceptual pureness of it all, rather than practical concerns. :-)
If we have a mini to build on, this issue is a non-practical concern entirely, then we'll just build there and it'll just work.
But we'll still be doing it wrong.
famous last words!
No branches or pull requests
Just the obvious example: We use
buildInputs
everywhere instead of distinguishing it fromnativeBuildInputs
.I don't currently know if our racket package derivations are platform-specific or not. Are
*.zo
files platform-specific?Not a high priority, but if we're lucky it might enable hydra to make some of the packages for darwin without involving darwin.
The text was updated successfully, but these errors were encountered: