Skip to content

Conversation

@angerman
Copy link
Collaborator

No description provided.

@rvl
Copy link
Contributor

rvl commented May 7, 2019

Seems like it will work. Could there be test cases which check executables are stripped or not depending on the option?

@angerman
Copy link
Collaborator Author

I've just locally confimed this will work. I'm trying my luck with a test case now.

@angerman
Copy link
Collaborator Author

I fail to get anywhere with a proper testcase for this. As such I'll just go and merge this. While file on linux would give you some indication of stripped or non-stripped, I can't seem to get this working on macOS.

@angerman angerman merged commit ff3b316 into master May 13, 2019
andreabedini pushed a commit to andreabedini/haskell.nix that referenced this pull request Sep 14, 2022
…#110)

If a package is local to the project, but none of the components are in the plan, then there will be an empty `components` attribute and no `component-name`.  Currently this causes an error as we look for a `component-name` when the `components` attribute is empty.  This change will make it so that we only look for the `component-name` when there is no `components` attribute at all.
andreabedini pushed a commit to andreabedini/haskell.nix that referenced this pull request Sep 14, 2022
…#110)

If a package is local to the project, but none of the components are in the plan, then there will be an empty `components` attribute and no `component-name`.  Currently this causes an error as we look for a `component-name` when the `components` attribute is empty.  This change will make it so that we only look for the `component-name` when there is no `components` attribute at all.
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

Successfully merging this pull request may close these issues.

3 participants