Mercurial > hg
view contrib/wix/README.txt @ 26441:56527b886d1d
streamclone: move applystreamclone() from localrepo.py
Upcoming patches will modernize the streaming clone code. Streaming
clone data and code kind of lives in its own world. exchange.py is
arguably the most appropriate existing location for it. However, over
a dozen patches from now it became apparent that there was a lot of code
related to streaming clones and that having it contained within its own
module would make it easier to comprehend. So, we establish
streamclone.py.
It's worth noting that streamclone.py existed a long time ago, last seen
in the 1.6 release. It was removed in 04f76a954842.
The function was renamed as part of the move because its old name was
redundant with the new module name. The only other content change was
"self" was renamed to "repo" and minor grammar in the docstring was
updated.
author | Gregory Szorc <gregory.szorc@gmail.com> |
---|---|
date | Fri, 02 Oct 2015 15:51:32 -0700 |
parents | 98166640b356 |
children | 765f836a9484 |
line wrap: on
line source
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 the only sane way to keep the source tree and the installer in sync. 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 under the C:\WINDOWS\WinSxS folder. Thus the InnoSetup installers may still be useful to some users. 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/