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

[Do not merge*] Restore stdenv debugging at the cost of more complexity #20889

Closed
wants to merge 1 commit into from

Conversation

Ericson2314
Copy link
Member

#15043 simplifies and cleans up the way stdenvs are bootstrapped, at the cost of removing potentially useful debugging aids. This adds back debugging aids at least as useful as the old ones, but at the cost of some complexity (though the extra stuff should all be dead code when not debugging.)

I'm, not sure whether this is a good idea or not--my hope is that by opening this anyone who's workflows are gummed up by #15043 has somewhere to turn. If that's you, feel free to merge.

@mention-bot
Copy link

@Ericson2314, thanks for your PR! By analyzing the history of the files in this pull request, we identified @nbp, @edolstra and @copumpkin to be potential reviewers.

Ericson2314 added a commit to Ericson2314/nixpkgs that referenced this pull request Dec 4, 2016
 - The darwin test can now force the use of the freshly-booted darwin stdenv
 - The linux test now passes enough dummy arguments

This may make debugging harder, if so, check out NixOS#20889
@Ericson2314
Copy link
Member Author

I've debugged stdenv plenty of times the past year, and never once needed missed this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants