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

Re-invert behavior of --no-substitute-on-destination #386

Merged
merged 2 commits into from
Sep 19, 2024

Conversation

chreekat
Copy link
Contributor

Maybe there's a better way to do this, but it looks like removing elements from an array is kind of a pain.

@Mic92
Copy link
Member

Mic92 commented Sep 18, 2024

@chreekat please test again.

@Mic92 Mic92 force-pushed the b/fix-substitute-on-destination branch from 71c9a04 to 95efb19 Compare September 18, 2024 14:29
@chreekat
Copy link
Contributor Author

I don't have a spare target machine atm, but I like your version better and it "looks right" 🚀 .

@Mic92 Mic92 merged commit e4af92b into nix-community:main Sep 19, 2024
4 checks passed
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.

2 participants