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

Use specific version of libc #563

Closed
wants to merge 1 commit into from
Closed

Conversation

Susurrus
Copy link
Contributor

It should be policy for additional functionality to wait for a libc release anyways before nix can release, so these should just bump the libc dependency version anyways.

@Susurrus
Copy link
Contributor Author

Probably #565 should be merged instead of this, though a policy should be set on whether we want to depend only on released versions for dependencies or using git directly is fine. @posborne @fiveop Any comments on this or should I bring it up on nix-rust/rfcs?

@kamalmarhubi
Copy link
Member

Right now we set a fixed version at release time, and otherwise leave it tracking the repository. This allows someone to add a feature to nix and libc without requiring a release of libc until we want to release nix. It's weird, but I think it's a nice way not to force lots of libc releases to make progress on nix.

@kamalmarhubi
Copy link
Member

I merged #565 so I'm going to close this. But please reopen and/or start a new discussion if you want to chat more about it!

@Susurrus Susurrus deleted the libc_dep branch July 13, 2017 19:14
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.

None yet

2 participants