- 03 Feb, 2021 1 commit
-
-
Matt Harbison authored
-
- 26 Jan, 2021 1 commit
-
-
Matt Harbison authored
-
- 24 Jan, 2021 1 commit
-
-
Matt Harbison authored
-
- 31 Oct, 2020 1 commit
-
-
Matt Harbison authored
-
- 29 Oct, 2020 1 commit
-
-
Matt Harbison authored
The former was extracted from the TortoiseSVN-1.14.0.28885 MSI with lessMSI 1.7, and the latter was downloaded from https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html.
-
- 10 Sep, 2020 1 commit
-
-
Matt Harbison authored
-
- 08 Aug, 2020 1 commit
-
-
Matt Harbison authored
-
- 30 Jul, 2020 1 commit
-
-
Matt Harbison authored
The tag isn't applied yet, but something with phases is no longer hashable, so an update is needed.
-
- 08 Jul, 2020 2 commits
-
-
Matt Harbison authored
The `meu` repo update is just to pick up documents that stop referencing BitBucket.
-
Matt Harbison authored
These are needed for the upgrade checks that call out to the website, which hasn't worked since 07c551483c40.
-
- 20 May, 2020 1 commit
-
-
Matt Harbison authored
-
- 10 Apr, 2020 1 commit
-
-
Matt Harbison authored
-
- 08 Mar, 2020 1 commit
-
-
Matt Harbison authored
-
- 05 Mar, 2020 1 commit
-
-
Matt Harbison authored
-
- 15 Feb, 2020 1 commit
-
-
Matt Harbison authored
The packaging scripts in 5.3 handle building this when given a 32-bit python and MSVC 2015, or at least MS Build Tools 2015[1]. [1] https://visualstudio.microsoft.com/vs/older-downloads/
-
- 12 Feb, 2020 1 commit
-
-
Matt Harbison authored
This is required to build with thg 9e3bf37dd711 (just prior to 5.3-rc0).
-
- 06 Feb, 2020 2 commits
-
-
Matt Harbison authored
I have no idea where dulwich went- this seems autogenerated. I had to install it into the virtualenv at one point, but that's easy enough to do.
-
Matt Harbison authored
I have no idea why my Windows 10 (1909) system wants to include what looks like older API DLLs. I tried, but failed to figure out how to hack the build process to exclude these by prefix.
-
- 30 Jan, 2020 1 commit
-
-
Matt Harbison authored
-
- 19 Aug, 2019 1 commit
-
-
Steve Borho authored
-
- 02 Aug, 2019 1 commit
-
-
Matt Harbison authored
-
- 14 Jul, 2019 2 commits
-
-
Matt Harbison authored
This means that any command prompt will properly build everything, whereas before the 'Visual C++ 2008 64-bit Cross Tools Command Prompt' was required. The goal is to remove a point of failure (the plain 64-bit prompt fails), and to move towards automated builds like core Mercurial. I've only got the Express edition at home (which fails to build this), so I'm not doing the same for Visual Studio 2008.
-
Matt Harbison authored
The build process already builds Mercurial with this compiler if it is installed, so we might as well use this to compile the shell extension if it is available. The only manual change needed is to download these merge modules: vc9-crt-x64-msm vc9-crt-x64-msm-policy create 'Redist\VC' here: %LOCALAPPDATA%\Programs\Common\Microsoft\Visual C++ for Python\9.0\WinSDK\ and name them: Microsoft.VCxx.CRT.x64_msm.msm policy.x.xx.Microsoft.VCxx.CRT.x64_msm.msm I have no idea why, but DISTUTILS_USE_SDK can't be set, otherwise Mercurial fails to build its C extensions. The strange thing is that the new packaging scripts *do* set this. [1] https://github.com/indygreg/vc90-merge-modules
-
- 13 Jul, 2019 2 commits
-
-
Matt Harbison authored
-
Matt Harbison authored
-
- 23 Jul, 2019 1 commit
-
-
Steve Borho authored
allow py2exe to pick up the dulwich compiled and installed by pip
-
- 14 Apr, 2019 3 commits
-
-
Steve Borho authored
-
Steve Borho authored
-
Steve Borho authored
-
- 24 Feb, 2019 2 commits
-
-
Steve Borho authored
-
Steve Borho authored
-
- 19 Jan, 2019 1 commit
-
-
Steve Borho authored
-
- 10 Dec, 2018 5 commits
-
-
Steve Borho authored
-
Steve Borho authored
-
Steve Borho authored
-
Steve Borho authored
-
Steve Borho authored
-
- 29 Oct, 2018 1 commit
-
-
Paul Morelle authored
Version tags of the form '4.8-rc0' were already supported, but apparently the format has changed since then.
-
- 14 Nov, 2018 2 commits
-
-
Steve Borho authored
this repo hasn't seen any code changes in 3 years, stop tagging it for every release. Assume all releases from 4.8 onward use the tip
-
Steve Borho authored
There are a few command line behavior changes. * The build targets no longer use -- prefixes, aka: setup.py thg-release [OPTIONS] * --all has been removed, I don't believe worked anymore * --pull is now the default, and is implied * Unless --nopull is specified, repos are pulled before detecting latest tags
-