Why is the file not being required as a dependency? Is it a rebar policy to not fetch dependencies using rebar? (i understand that it could be an issue if rebar was broken, but could be easily solved using the last stable build, wouldn't it?)

I rebased. Since you guys renamed original getopt to rebar_getopt module, it doesn't seem there is any more dependency on the jcomellas/getopt#25 pull request. It's up to you if you want to add this functionality to rebar_getopt, but I find it quite useful. Read "Checking required options" and "Converting parsed list of arguments to a record" in https://github.com/saleyn/getopt/blob/format_error/README.md.

Hi, this issue was closed in an attempt to do quick basic filtering, with the benediction of rebar project owners. These issues and pull requests are not issues or code we're spitting on, but given the burden of the task and how much code rot may have happened since these were open is unknown from maintainers at this time. All tickets prior to March 2014 were closed and will be reopened on a per-request basis if we see interest from the reporter or contributor, or if some of the issues reported are still valid after the various patches that have made it since they were opened.

This is a fairly brutal first step to help us get a proper understanding of what is still valid or not, but that has been proven efficient in the past. Sorry for the inconvenience, things should go smoother from there on.

It seems to me that there's no longer a need to wait for merging of the patch by jcomellas since rebar_getopt was renamed from getopt and now lives in rebar by its own. Though the proposed additions to getopt don't functionally add anything to rebar, they do add ability to validate options and throw exceptions, as well as convert the parsed options to a record for easier processing, which is something rebar could use at some point down the line.