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

Adding libsecret to cargo to get cargo login to work #190

Merged
merged 3 commits into from
Oct 9, 2024

Conversation

P-E-Meunier
Copy link
Contributor

On Linux, the recommended way to work with cargo login is via libsecret, but that requires a specific LD_LIBRARY_PATH with this overaly.

This PR fixes this by adding libsecret as a runtime dependency of cargo.

Tested on Linux-aarch64.

Copy link
Owner

@oxalica oxalica left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it should go mk-component-set.nix because it's specific about cargo itself, instead of the integrated toolchain.

Copy link
Owner

@oxalica oxalica left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Otherwise LGTM. Works for me.

@@ -1,4 +1,4 @@
{ lib, stdenv, symlinkJoin, pkgsTargetTarget, bash, curl }:
{ lib, stdenv, symlinkJoin, pkgsTargetTarget, bash, curl, libsecret }:
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Forget to remove this?

@oxalica
Copy link
Owner

oxalica commented Oct 9, 2024

Hmm, the cross-compilation is failing because libsecret is somehow not targetPlatform-agnostic. I don't think it's intended and I'll look into it on nixpkgs later when I have time.

But for now, let's explicitly use ${pkgsHostHost.libsecret}. It should workaround the issue.

@oxalica oxalica merged commit e310b9b into oxalica:master Oct 9, 2024
31 checks passed
@oxalica
Copy link
Owner

oxalica commented Oct 9, 2024

Thanks!

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