tests/test-eol-tag.t

packaging: bundle dulwich, keyring, and pywin32-ctypes with WiX too

TortoiseHg installs these, which is possibly where they originated (though I
would have thought it more likely to be in the WiX installer, given its
heritage).  When I was working on the TortoiseHg app for Mac (which uses the
similar `py2app`), it wasn't possible to use the keyring extension (even
externally) without bundling this keyring package into the app.  Assuming the
same principle applies here, these would enable some common extensions.  One of
the things that the TortoiseHg packager on macOS does now is it adds the user's
local `site-packages` directory to `sys.path`.  That would allow the user to
install these critical modules in cases like this.  But that can probably wait
for py3 packaging.

The only difference in the installed packages that I see now is WiX also bundles
distutils for some reason.  I suppose that's not harming anything, so I'm not
touching it.

The only orphans in the install directories when comparing WiX and Inno now is
the Copying.txt vs COPYING.rtf, the two uninstaller files for Inno, and a
`Mercurial.url` file in Inno.  I have no idea what that is, and it has *.ini
syntax with a single field pointing to the Mercurial homepage.

Differential Revision: https://phab.mercurial-scm.org/D8062

https://bz.mercurial-scm.org/2493

Testing tagging with the EOL extension

  $ cat >> $HGRCPATH <<EOF
  > [extensions]
  > eol =
  > 
  > [eol]
  > native = CRLF
  > EOF

setup repository

  $ hg init repo
  $ cd repo
  $ cat > .hgeol <<EOF
  > [patterns]
  > ** = native
  > EOF
  $ printf "first\r\nsecond\r\nthird\r\n" > a.txt
  $ hg commit --addremove -m 'checkin'
  adding .hgeol
  adding a.txt

Tag:

  $ hg tag 1.0

Rewrite .hgtags file as it would look on a new checkout:

  $ hg update -q null
  $ hg update -q

Touch .hgtags file again:

  $ hg tag 2.0

  $ cd ..