Mercurial > hg
view contrib/win32/buildlocal.bat @ 30832:da5fa0f13a41
ui: introduce an experimental dict of exportable environment variables
Care needs to be taken to prevent leaking potentially sensitive environment
variables through hgweb, if template support for environment variables is to be
introduced. There are a few ideas about the API for preventing accidental
leaking [1]. Option 3 seems best from the POV of not needing to configure
anything in the normal case. I couldn't figure out how to do that, so guard it
with an experimental option for now.
[1] https://www.mercurial-scm.org/pipermail/mercurial-devel/2017-January/092383.html
| author | Matt Harbison <matt_harbison@yahoo.com> |
|---|---|
| date | Tue, 17 Jan 2017 23:05:12 -0500 |
| parents | 70ef5b610222 |
| children |
line wrap: on
line source
@echo off rem Double-click this file to (re)build Mercurial for Windows in place. rem Useful for testing and development. cd ..\.. del /Q mercurial\*.pyd del /Q mercurial\*.pyc rmdir /Q /S mercurial\locale python setup.py build_py -c -d . build_ext -i build_mo pause