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

Clean, generic, language-agnostic cross-compilation-aware core build infrastructure #36217

Closed
3 tasks
shlevy opened this issue Mar 2, 2018 · 3 comments
Closed
3 tasks
Assignees

Comments

@shlevy
Copy link
Member

shlevy commented Mar 2, 2018

TODO @Ericson2314 fill this out

  1. Make mkDerivation a wrapper that desugars the legacy input names as proposed above. No more {propagated,}{Native,}BuildInputs in bash.

  2. Move away from autoconf terminology to build, run, emit (isomorphic renaming).

  3. Make env hooks more coarse-grained, I see no use for the second axis for them.

Action item from #35543

@stale
Copy link

stale bot commented Jun 5, 2020

Thank you for your contributions.

This has been automatically marked as stale because it has had no activity for 180 days.

If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.

Here are suggestions that might help resolve this more quickly:

  1. Search for maintainers and people that previously touched the related code and @ mention them in a comment.
  2. Ask on the NixOS Discourse.
  3. Ask on the #nixos channel on irc.freenode.net.

@stale stale bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jun 5, 2020
@siraben
Copy link
Member

siraben commented Jan 18, 2021

Any updates on this?

@stale stale bot removed the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jan 18, 2021
@Ericson2314
Copy link
Member

I would say I never filled this out, and the first steps are tracked in issue #28327 and PR #72074. Perhaps we want larger changes, but I'd say that hinges on larger cleanups of Nixpkgs in general.

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

3 participants