-
Notifications
You must be signed in to change notification settings - Fork 666
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
Add a fchownat(2) wrapper #955
Conversation
Per the TODO, do you think The way I'd validate that is: add a trivial test for I can do this before the merge; just let me know if there are other considerations. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A successful Travis run is insufficient for removing a binding. We need to make sure that the newer alternative is supported on all Nix platforms, including those that aren't tested in CI, like NetBSD and OpenBSD. Though in this case, I don't think there's much to be gained by removing chown
. Since it's required by POSIX, OSes won't ever drop it from their C libraries. And it doesn't cost anything to keep around. Do you agree?
9740612
to
aec00bd
Compare
I don't mind keeping In fact, I think that if the OS exposes such functions, they should be exposed in |
The same rationale would apply to |
I've added tests to ensure these functions exists in all CI platforms, and also confirmed in my project that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This LGTM now. But I think you should remove the mention of deprecating chown
from your commit message. I don't think we should ever remove chown
.
These are mostly to ensure that all the platforms we care about in our CI can reference these primitives.
Updated the commit message and removed the original contents of the PR message, which I think would be added to the history as well. Also rebased on top of the truncate merge to avoid |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bors r+
No description provided.