##// END OF EJS Templates
upstream » mercurial-mirror
RSS

Clone from https://www.mercurial-scm.org/repo/hg-all

bundle1: fix bundle1-denied reporting for pull over ssh...
bundle1: fix bundle1-denied reporting for pull over ssh Changeset b288fb2724bf introduced a config option to have the server deny pull using bundle1. The original protocol has not really been design to allow that kind of error reporting so some hack was used. It turned the hack only works on HTTP and that ssh server hangs forever when this is used. After further digging, there is no way to report the error in a unified way. Using `ooberror` freeze ssh and raising 'Abort' makes HTTP return a HTTP-500 without further details. So with sadness we implement a version that dispatch according to the protocol used. Now the error is properly reported, but we still have ungraceful abort after that. The protocol do not allow anything better to happen using bundle1.
Mads Kiilerich - - Load All Authors

File last commit:

r17251:98166640 stable
r30912:3d4afc2f stable
Show More
README.txt
31 lines | 1.4 KiB | text/plain | TextLexer
/ contrib / wix / README.txt
History | Source | Raw |Copy content |Copy permalink
Steve Borho
Add WiX installer scripts to contrib/wix
 r10502 WiX installer source files
==========================
The files in this folder are used by the thg-winbuild [1] package
building architecture to create a Mercurial MSI installer. These files
are versioned within the Mercurial source tree because the WXS files
must kept up to date with distribution changes within their branch. In
other words, the default branch WXS files are expected to diverge from
the stable branch WXS files. Storing them within the same repository is
Mads Kiilerich
help: fix some instances of 'the the'
 r17251 the only sane way to keep the source tree and the installer in sync.
Steve Borho
Add WiX installer scripts to contrib/wix
 r10502
The MSI installer builder uses only the mercurial.ini file from the
contrib/win32 folder, the contents of which have been historically used
to create an InnoSetup based installer. The rest of the files there are
ignored.
The MSI packages built by thg-winbuild require elevated (admin)
privileges to be installed due to the installation of MSVC CRT libraries
Adrian Buehlmann
contrib/wix: MSVC CRT libraries are installed in WinSxS...
 r10503 under the C:\WINDOWS\WinSxS folder. Thus the InnoSetup installers may
still be useful to some users.
Steve Borho
Add WiX installer scripts to contrib/wix
 r10502
To build your own MSI packages, clone the thg-winbuild [1] repository
and follow the README.txt [2] instructions closely. There are fewer
prerequisites for a WiX [3] installer than an InnoSetup installer, but
they are more specific.
Direct questions or comments to Steve Borho <steve@borho.org>
[1] http://bitbucket.org/tortoisehg/thg-winbuild
[2] http://bitbucket.org/tortoisehg/thg-winbuild/src/tip/README.txt
[3] http://wix.sourceforge.net/