view CONTRIBUTING @ 49836:3d7bf111f01e stable

packaging: add dependencies to the PyOxidizer build on macOS

Otherwise, we get a bunch of test failures for missing things like pygments, or
tests skipped entirely.  The input file is a copy/paste from the equivalent
Windows file, but with dulwich, pygit2, and pytest-vcr commented out because
the build process errors out with them, flagging them as incompatible with
loading from memory.  I have no idea if that's actually true or not, because
I've noticed that if I don't `make clean` after every build, the next build
flags the watchman stuff as incompatible with loading from memory.

The remaining failures are:

    Failed test-alias.t: output changed
    Failed test-basic.t: output changed
    Failed test-check-help.t: output changed
    Failed test-commit-interactive.t: output changed
    Failed test-extension.t: output changed
    Failed test-help.t: output changed
    Failed test-i18n.t: output changed
    Failed test-log.t: output changed
    Failed test-qrecord.t: output changed
    Failed test-share-safe.t: output changed

Most of the issues seem related to loading help for disabled extensions from
`hgext.__index__`, namely the full extension help being unavailable, not being
able to resolve what commands are provided by what extension, and not having the
command level help available.

test-log.t, test-commit-interactive.t, and test-i18n.t look like i18n (or lack
thereof) issues.

test-basic.t is just odd:
    @@ -55,7 +55,7 @@
     On Python 3, stdio may be None:

       $ hg debuguiprompt --config ui.interactive=true 0<&-
    -   abort: Bad file descriptor (no-rhg !)
    +   abort: response expected
        abort: response expected (rhg !)
       [255]
       $ hg version -q 0<&-

Our full contribution guidelines are in our wiki, please see:

https://www.mercurial-scm.org/wiki/ContributingChanges

If you just want a checklist to follow, you can go straight to

https://www.mercurial-scm.org/wiki/ContributingChanges#Submission_checklist

If you can't run the entire testsuite for some reason (it can be
difficult on Windows), please at least run `contrib/check-code.py` on
any files you've modified and run `python contrib/check-commit` on any
commits you've made (for example, `python contrib/check-commit
273ce12ad8f1` will report some style violations on a very old commit).