-
Notifications
You must be signed in to change notification settings - Fork 689
Re-adding execvpe support, conditional on platform #683
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
Conversation
You'll need to do a few more things:
|
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.
Looking pretty good. Also needs a CHANGELOG entry and to have all commits except for the one that changes the libc
dependency to be squashed into one (see the git rebase
command).
src/unistd.rs
Outdated
/// * `env`: array of environment variables for the new execution environment | ||
/// * returns: Ok or libc error code. | ||
/// | ||
/// Err is returned if the executable file does not exist, cannot be accessed, or |
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.
Instead of "Err" use "An error"
src/unistd.rs
Outdated
}; | ||
|
||
Err(Error::Sys(Errno::last())) | ||
Errno::result(res).map(drop) |
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.
Indentation here is off by 1.
I have made all the requested changes, but I cannot squash all the changes into two commits as described. I've tried |
src/unistd.rs
Outdated
/// Replaces the current process image with a new one. | ||
/// ([see exec(3)](http://man7.org/linux/man-pages/man3/exec.3.html)) | ||
/// | ||
/// * `filename`: filename of executable to run |
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.
Can you give a title or quick sentence to introduce this bulleted list? It doesn't read nicely just being a stand alone list.
src/unistd.rs
Outdated
/// * `env`: array of environment variables for the new execution environment | ||
/// * returns: Ok or libc error code. | ||
/// | ||
/// An error is returned if the executable file does not exist, cannot be accessed, or |
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.
There is a special section called Errors
that you should use for these kinds of things. See the book.
src/unistd.rs
Outdated
/// * `filename`: filename of executable to run | ||
/// * `args`: array of arguments as strings; first must be the filename | ||
/// * `env`: array of environment variables for the new execution environment | ||
/// * returns: Ok or libc error code. |
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 can be handled by the Errors
section below.
I would like to get these commits squashed, you said you couldn't do that, is that because you aren't familiar with |
I followed the exact procedure described there and the rebase failed. |
You'll need to fix merge commits when you rebase sometimes, so if there's a conflict it isn't a "failure" it just means you need to manually merge some of the code. |
Well, if that's the case, someone else needs to do it. |
This isn't that bad to fix and it's probably worth getting a little bit more familiar with This looks like:
Now, if more changes need to be made:
Let me know if you get stuck doing any of that. Hopefully it all makes sense now! |
fatal: 'upstream' does not appear to be a git repository |
You may have it called "origin"; do |
There was no remote set for the upstream repo. |
Yeah, the default would be to have "origin" set to your repo. So let's add an upstream:
|
I already did that. |
What's the output of |
Have you noticed that there are new commits? |
Oh, perfect, I did not. I've been squatting on this page and GitHub's terrible at dealing with force-pushing things, so I was still seeing 12 commits or whatever. So this wraps in some changes that are part of the commits in #681 into your own commits, which isn't ideal, but fine. What we'll do is wait until that's merged, rebase this (which will get rid of all of those code changes) and then this'll be ready to merge! Thanks for sticking with this, git can be really frustrating sometimes, but I've found it quite powerful now that I've really gotten the hang of it. |
@panzertime Want to rerebase this and clean up the remaining issues? This is pretty close to merging. |
What issues remain? |
@@ -24,6 +24,8 @@ This project adheres to [Semantic Versioning](http://semver.org/). | |||
and nix::Error::UnsupportedOperation}` | |||
([#614](https://github.com/nix-rust/nix/pull/614)) | |||
- Added `cfmakeraw`, `cfsetspeed`, and `tcgetsid`. ([#527](https://github.com/nix-rust/nix/pull/527)) | |||
- Readded execvpe support, conditional on platform. libc now provides this for Haiku, Linux, and OpenBSD. |
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.
Change to "Added unistd::execvpe
for Haiku, Linux, and OpenBSD."
Just the CHANGELOG entry should be more clear & concise. Otherwise this needs a rebase and then it should be good. Though I want to take another look over it once it's rebased as it's hard to tell what the actual changes are here since there are some other things that seem mixed in here. |
@panzertime Just pinging you on this since we were getting pretty close to merging this. Can you rebase and address my comments? |
@panzertime It's been a month since I last pinged you, so I wanted to do that again and see if we could get this merged. |
@panzertime I think it's just the changelog entry now and a rebase and this is good to go. Still interested in merging this? |
It's been almost 5 months on this with several pings, so I'm going to go ahead and close this PR. |
Fixes #682