blocks|key|337807|text|正如第397期中提到的|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|337808|这是故意的。我们不附带Git+for+Windows的pacman。
如果您对一个成熟的包管理器维护环境感兴趣，那么您必须尝试一下Git+for+Windows+SDK。|blockquote|337809|您在Windows最新git+(2.5.3)+(这是一个最近的一次比旧的+)中看到的bash仅用于执行git命令。|337810|安装任何第三方程序包都不是一个成熟的linux环境。|337811|警告：评论中的杜杰报告|style|BOLD|337812|不要使用目录连接将现有的链接到msys2主系统。
如果卸载，它将决定链接目录属于它，并删除整个主目录，包括像“下载”这样的子目录。
小心与msys2打交道。
我不知道windows中的是否也是如此，但是要小心地尝试从其他系统中获取pacman和用于windows的git集成。|337813|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/git-for-windows/git/issues/397#issuecomment-140984199|1|https://github.com/git-for-windows/build-extra/releases|2|3|4|https://stackoverflow.com/questions/32712133/package-management-in-git-for-windows/32713347#comment117719281_32713347|5|https://stackoverflow.com/users/1259706/dhj^0|2|5|0|0|1T|J|1|0|2|K|2|S|8|3|0|0|0|2|3|2|4|7|2|5|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@$A|17|B|18|1|19]]|C|$]]|$1|D|3|E|5|F|7|1A|8|@]|9|@$A|1B|B|1C|1|1D]]|C|$]]|$1|G|3|H|5|6|7|1E|8|@]|9|@$A|1F|B|1G|1|1H]|$A|1I|B|1J|1|1K]]|C|$]]|$1|I|3|J|5|6|7|1L|8|@]|9|@]|C|$]]|$1|K|3|L|5|6|7|1M|8|@$A|1N|B|1O|M|N]]|9|@$A|1P|B|1Q|1|1R]|$A|1S|B|1T|1|1U]]|C|$]]|$1|O|3|P|5|F|7|1V|8|@]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|1W|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]|Y|$5|T|U|V|C|$W|Z]]|10|$5|T|U|V|C|$W|X]]|11|$5|T|U|V|C|$W|Z]]|12|$5|T|U|V|C|$W|13]]|14|$5|T|U|V|C|$W|15]]]]

As mentioned in <a href="https://github.com/git-for-windows/git/issues/397#issuecomment-140984199" rel="noreferrer">issue 397</a>:
<blockquote>
This is intended. We do not ship pacman with Git for Windows. 
If you are interested in a fully fledged package manager maintained environment you have to give the <a href="https://github.com/git-for-windows/build-extra/releases" rel="noreferrer">Git for Windows SDK</a> a try.
</blockquote>
The bash that you see in the <a href="https://github.com/git-for-windows/git/issues/397#issuecomment-140984199" rel="noreferrer">latest git for Windows (2.5.3)</a>, which is a <a href="https://github.com/git-for-windows/build-extra/releases" rel="noreferrer">more recent bash than the old msysgit one</a>, is only there to execute git commands. 
It is not a full-fledged linux environment to install any third-party package.
<hr />
Warning: <a href="https://stackoverflow.com/users/1259706/dhj">dhj</a> reports in <a href="https://stackoverflow.com/questions/32712133/package-management-in-git-for-windows/32713347#comment117719281_32713347">the comments</a>
<blockquote>
Do not link your existing git for windows with the msys2 main system by using a directory junction. 
If you uninstall it will decide that linked directory belongs to it and DELETE YOUR ENTIRE HOME DIRECTORY including sub-directories like &quot;Downloads&quot;. 
Beware dealing with msys2.
I don't know if the same is true for the git for windows SDK, but BE CAREFUL trying to get pacman from other systems integrated with git for windows.
</blockquote>

blocks|key|1503961|text|Git+(https://gitforwindows.org/或https://git-scm.com/downloads)有Git，但不包括tree。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1503962|tree可以通过pacman+(软件包管理器)获得，但只有在安装“”(滚动到https://gitforwindows.org/底部，它提供了从https://github.com/git-for-windows/build-extra/releases/latest下载安装程序的链接)时才可用。|1503963|被接受的答案非常有用。他们提到git-for-windows不打算在默认安装中包括pacman。|1503964|因此，我安装了"Git+for+Windows+SDK"，然后在bash提示符(SDK-64)中运行以下命令来安装当前的树v1.7.0-1+(截至2018年8月30日)：|1503965|[SDK-64:+Bash+Terminal+for+Git+for+Windows+SDK]
pacman+-S+tree
...
Proceed+with+installation?+[Y/n]+Y|code-block|syntax|javascript|1503966|在我的系统中，Git安装在：C:\git-sdk-64下，因此，从我的(它没有安装树)中，我将它通过tree.exe复制到它的/usr/bin目录中。|1503967|[MINGW64:+Bash+Terminal+for+Git+for+Windows]
cd+/usr/bin
cp+/c/git-sdk-64/usr/bin/tree.exe+.|1503968|现在，我可以在两个Git上运行tree+v1.7.0。|1503969|为了让其他人，也许是我自己在未来的机器上更容易，我在getting终端中运行了以下命令，查看了pacman从哪里获得了tree包：|1503970|$+pacman+-S+--info+tree
Repository++++++:+msys
Name++++++++++++:+tree
Version+++++++++:+1.7.0-1
Description+++++:+A+directory+listing+program+displaying+a+depth+indented+list+of+files
Architecture++++:+x86_64
...|1503971|这里的关键是，pacman正在从"msys“存储库(FYI:尽管它说msys，它实际上正在使用msys2)获取tree，所以我查看了/etc/pacman.d/mirrorlist.msys，第一个镜像指向http://repo.msys2.org/msys/$arch/。|1503972|因此，下次当您想要一个不在Git中的包时，您可以从：[64]+(64位)或http://repo.msys2.org/msys/i686/+(32位)下载它们。|1503973|例如，树v1.7.0-1的直接下载链接|1503974|64位：64.pkg.tar.xz|unordered-list-item|1503975|或64.pkg.tar.xz|1503976|32位：http://repo.msys2.org/msys/i686/tree-1.7.0-1-i686.pkg.tar.xz|1503977|或https://sourceforge.net/projects/msys2/files/REPOS/MSYS2/i686/tree-1.7.0-1-i686.pkg.tar.xz|1503978|FYI:+GitHub窗口在https://git-scm.com/download/下载的最新版本来自GitHub+(https://github.com/git-for-windows/git来自https://github.com/git-for-windows/git/releases/链接)|1503979|entityMap|0|LINK|mutability|MUTABLE|url|https://gitforwindows.org/|1|https://git-scm.com/downloads|2|3|https://github.com/git-for-windows/build-extra/releases/latest|4|https://stackoverflow.com/a/32713347|5|http://repo.msys2.org/msys/x86_64/|6|http://repo.msys2.org/msys/i686/|7|http://repo.msys2.org/msys/x86_64/tree-1.7.0-1-x86_64.pkg.tar.xz|8|https://sourceforge.net/projects/msys2/files/REPOS/MSYS2/x86_64/tree-1.7.0-1-x86_64.pkg.tar.xz|9|http://repo.msys2.org/msys/i686/tree-1.7.0-1-i686.pkg.tar.xz|10|https://sourceforge.net/projects/msys2/files/REPOS/MSYS2/i686/tree-1.7.0-1-i686.pkg.tar.xz|11|https://git-scm.com/download/|12|https://github.com/git-for-windows/git|13|https://github.com/git-for-windows/git/releases/^0|1Z|4|5|Q|0|W|T|1|0|0|4|8|6|12|Q|2|20|1Q|3|0|F|F|15|6|0|6|4|0|0|0|E|D|1R|8|0|0|F|4|0|1B|6|1N|4|0|0|7|6|1J|4|1U|T|2V|X|0|Q|4|5|11|W|6|0|0|4|D|7|0|1|D|8|0|4|1O|9|0|1|2I|A|0|E|T|B|1O|12|C|2S|1C|D|0^^$0|@$1|2|3|4|5|6|7|2E|8|@$9|2F|A|2G|B|C]]|D|@$9|2H|A|2I|1|2J]|$9|2K|A|2L|1|2M]]|E|$]]|$1|F|3|G|5|6|7|2N|8|@$9|2O|A|2P|B|C]|$9|2Q|A|2R|B|C]]|D|@$9|2S|A|2T|1|2U]|$9|2V|A|2W|1|2X]]|E|$]]|$1|H|3|I|5|6|7|2Y|8|@$9|2Z|A|30|B|C]|$9|31|A|32|B|C]]|D|@$9|33|A|34|1|35]]|E|$]]|$1|J|3|K|5|6|7|36|8|@]|D|@]|E|$]]|$1|L|3|M|5|N|7|37|8|@]|D|@]|E|$O|P]]|$1|Q|3|R|5|6|7|38|8|@$9|39|A|3A|B|C]|$9|3B|A|3C|B|C]]|D|@]|E|$]]|$1|S|3|T|5|N|7|3D|8|@]|D|@]|E|$O|P]]|$1|U|3|V|5|6|7|3E|8|@$9|3F|A|3G|B|C]]|D|@]|E|$]]|$1|W|3|X|5|6|7|3H|8|@$9|3I|A|3J|B|C]|$9|3K|A|3L|B|C]]|D|@]|E|$]]|$1|Y|3|Z|5|N|7|3M|8|@]|D|@]|E|$O|P]]|$1|10|3|11|5|6|7|3N|8|@$9|3O|A|3P|B|C]|$9|3Q|A|3R|B|C]|$9|3S|A|3T|B|C]|$9|3U|A|3V|B|C]]|D|@]|E|$]]|$1|12|3|13|5|6|7|3W|8|@]|D|@$9|3X|A|3Y|1|3Z]|$9|40|A|41|1|42]]|E|$]]|$1|14|3|15|5|6|7|43|8|@]|D|@]|E|$]]|$1|16|3|17|5|18|7|44|8|@]|D|@$9|45|A|46|1|47]]|E|$]]|$1|19|3|1A|5|18|7|48|8|@]|D|@$9|49|A|4A|1|4B]]|E|$]]|$1|1B|3|1C|5|18|7|4C|8|@]|D|@$9|4D|A|4E|1|4F]]|E|$]]|$1|1D|3|1E|5|18|7|4G|8|@]|D|@$9|4H|A|4I|1|4J]]|E|$]]|$1|1F|3|1G|5|6|7|4K|8|@]|D|@$9|4L|A|4M|1|4N]|$9|4O|A|4P|1|4Q]|$9|4R|A|4S|1|4T]]|E|$]]|$1|1H|3|-4|5|6|7|4U|8|@]|D|@]|E|$]]]|1I|$1J|$5|1K|1L|1M|E|$1N|1O]]|1P|$5|1K|1L|1M|E|$1N|1Q]]|1R|$5|1K|1L|1M|E|$1N|1O]]|1S|$5|1K|1L|1M|E|$1N|1T]]|1U|$5|1K|1L|1M|E|$1N|1V]]|1W|$5|1K|1L|1M|E|$1N|1X]]|1Y|$5|1K|1L|1M|E|$1N|1Z]]|20|$5|1K|1L|1M|E|$1N|21]]|22|$5|1K|1L|1M|E|$1N|23]]|24|$5|1K|1L|1M|E|$1N|25]]|26|$5|1K|1L|1M|E|$1N|27]]|28|$5|1K|1L|1M|E|$1N|29]]|2A|$5|1K|1L|1M|E|$1N|2B]]|2C|$5|1K|1L|1M|E|$1N|2D]]]]

Git for Windows (<a href="https://gitforwindows.org/" rel="noreferrer">https://gitforwindows.org/</a> or <a href="https://git-scm.com/downloads" rel="noreferrer">https://git-scm.com/downloads</a>) has Git Bash but it does not include <code>tree</code>.
<code>tree</code> is available via <code>pacman</code> (Package Manager), but that is only available if you install &quot;Git for Windows SDK&quot; (scroll to the bottom of <a href="https://gitforwindows.org/" rel="noreferrer">https://gitforwindows.org/</a> which provides a link to download installer for it from <a href="https://github.com/git-for-windows/build-extra/releases/latest" rel="noreferrer">https://github.com/git-for-windows/build-extra/releases/latest</a>)
<a href="https://stackoverflow.com/a/32713347">The accepted answer</a> was very helpful. They mention that <code>git-for-windows</code> was not meant to include <code>pacman</code> in the default install.
So I installed &quot;Git for Windows SDK&quot;, then in its bash prompt (SDK-64) I ran the
following to install current tree v1.7.0-1 (as of this posting Aug 30, 2018):
<pre><code>[SDK-64: Bash Terminal for Git for Windows SDK]
pacman -S tree
...
Proceed with installation? [Y/n] Y
</code></pre>
On my system, Git for Windows SDK is installed under: <code>C:\git-sdk-64</code>, so from my Git for Windows Bash shell (which did not have tree installed), I copied it over tree.exe to its <code>/usr/bin</code> directory, e.g.
<pre><code>[MINGW64: Bash Terminal for Git for Windows]
cd /usr/bin
cp /c/git-sdk-64/usr/bin/tree.exe .
</code></pre>
Now I can run <code>tree</code> v1.7.0 from both Git Bash shells.
To make it even easier for others and maybe myself on a future machine, I looked at where <code>pacman</code> was getting the <code>tree</code> package from by running the following in my Git for Windows SDK Bash terminal:
<pre><code>$ pacman -S --info tree
Repository : msys
Name : tree
Version : 1.7.0-1
Description : A directory listing program displaying a depth indented list of files
Architecture : x86_64
...
</code></pre>
The key thing here is that <code>pacman</code> is getting <code>tree</code> from the &quot;msys&quot; repository (FYI: even though it says msys, it really is using msys2), so I looked at <code>/etc/pacman.d/mirrorlist.msys</code> and the first mirror points to <code>http://repo.msys2.org/msys/$arch/</code>
So next time you want a package that is NOT in Git for Windows, you can download them from: <a href="http://repo.msys2.org/msys/x86_64/" rel="noreferrer">http://repo.msys2.org/msys/x86_64/</a> (for 64-bit) or from <a href="http://repo.msys2.org/msys/i686/" rel="noreferrer">http://repo.msys2.org/msys/i686/</a> (32-bit)
e.g. direct download link for tree v1.7.0-1
<ul>
<li>64-bit: <a href="http://repo.msys2.org/msys/x86_64/tree-1.7.0-1-x86_64.pkg.tar.xz" rel="noreferrer">http://repo.msys2.org/msys/x86_64/tree-1.7.0-1-x86_64.pkg.tar.xz</a></li>
<li>or <a href="https://sourceforge.net/projects/msys2/files/REPOS/MSYS2/x86_64/tree-1.7.0-1-x86_64.pkg.tar.xz" rel="noreferrer">https://sourceforge.net/projects/msys2/files/REPOS/MSYS2/x86_64/tree-1.7.0-1-x86_64.pkg.tar.xz</a></li>
<li>32-bit: <a href="http://repo.msys2.org/msys/i686/tree-1.7.0-1-i686.pkg.tar.xz" rel="noreferrer">http://repo.msys2.org/msys/i686/tree-1.7.0-1-i686.pkg.tar.xz</a></li>
<li>or <a href="https://sourceforge.net/projects/msys2/files/REPOS/MSYS2/i686/tree-1.7.0-1-i686.pkg.tar.xz" rel="noreferrer">https://sourceforge.net/projects/msys2/files/REPOS/MSYS2/i686/tree-1.7.0-1-i686.pkg.tar.xz</a></li>
</ul>
FYI: Git SCM's Window's download at <a href="https://git-scm.com/download/" rel="noreferrer">https://git-scm.com/download/</a> pulls the latest from Git for Windows GitHub (<a href="https://github.com/git-for-windows/git" rel="noreferrer">https://github.com/git-for-windows/git</a> from the <a href="https://github.com/git-for-windows/git/releases/" rel="noreferrer">https://github.com/git-for-windows/git/releases/</a> link)

blocks|key|337893|text|似乎有一个记录方式可以这样做，而不必安装Git+(它非常大)。当我在GitHub+第1912期上询问所有这些信息时，GitHub给了我这个信息的链接。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|337894|下面是Git+wiki页面的当前文本：|337895|##Install在MSYS2本体中
###Please注意，不正式支持此方案
(这没有得到支持的原因是没有志愿者来支持这种情况。)
本指南假设您希望GitforWindows.的64位版本
Git基于MSYS2，可以将git包安装到现有的MSYS2安装中。这意味着，如果您已经在计算机上使用MSYS2，则可以在不运行完整安装程序或使用可移植版本的情况下使用。
然而，请注意，对于这种方式有一些警告。Git为msys2-runtime创建了一些尚未发送到上游的修补程序。(这是计划好的，但在#284问题中确定这可能不会发生。)这意味着您必须安装Git自定义msys2-runtime，才能在MSYS2中有一个完全工作的git。
在此，应采取的步骤：|blockquote|style|BOLD|CODE|337896|打开一个MSYS2终端。|ordered-list-item|337897|编辑/etc/pacman.conf，就在[mingw32]+(我的机器上的第71行)之前，添加git-for-windows包存储库：|337898|[git-for-windows]+Server+=+https://wingit.blob.core.windows.net/x86-64|337899|还可以选择只使用MINGW的相反体系结构的存储库(即64位SDK的MINGW32+)：|337900|[git-for-windows-mingw32]+Server+=+https://wingit.blob.core.windows.net/i686|337901|授权签名密钥(这个步骤可能会偶尔重复，直到https://github.com/msys2/msys2/issues/62被修复)|337902|curl+-L+https://raw.githubusercontent.com/git-for-windows/build-extra/master/git-for-windows-keyring/git-for-windows.gpg+%7C+pacman-key+--add+-+&&+pacman-key+--lsign-key+1A9F3986|337903|然后同步新的存储库。|337904|pacboy+update|337905|这将更新msys2-runtime，因此将要求您关闭窗口(而不仅仅是退出pacman进程)。不要惊慌，只需关闭所有当前打开的MSYS2+shell和MSYS2程序。重复检查任务管理器并杀死pacman.exe+--窗口关闭后仍在运行，因为它可能会逗留。一旦全部关闭，重新启动一个新的终端。|337906|然后再次同步(更新包的非核心部分)：|337907|pacboy+update|337908|最后，安装Git/cURL软件包：|337909|pacboy+sync+git:x+git-doc-html:x+git-doc-man:x+git-extra:+curl:x|337910|最后，通过在git+--version+shell中执行MINGW64，检查一切顺利，并且应该输出类似git+version+2.14.1.windows.1+(或更新)的内容。|337911|@VonC在评论中指出，在https://github.com/git-for-windows/git/issues/2688的讨论进行到一半的时候，人们正在讨论这种方法可能需要采取的其他步骤。|337912|现在，实现所需结果的一种可能的新方法是：|337913|https://github.com/git-for-windows/git/issues/2688#issuecomment-772311418|unordered-list-item|337914|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/git-for-windows/git/wiki/Install-inside-MSYS2-proper|1|https://github.com/git-for-windows/git/issues/1912|2|3|https://github.com/git-for-windows/git/issues/284|4|https://github.com/msys2/msys2/issues/62|5|https://github.com/git-for-windows/git/issues/2688|6^0|5|4|0|15|6|1|0|7|6|2|0|1V|M|32|3|5O|D|7Q|D|6T|4|3|0|0|2|G|L|9|1C|F|0|0|1Y|0|0|0|24|0|L|14|4|0|0|4W|0|0|0|D|0|4|D|2M|A|0|0|0|D|0|0|0|1S|0|6|D|1F|S|0|D|1E|5|0|0|0|21|6|0^^$0|@$1|2|3|4|5|6|7|25|8|@]|9|@$A|26|B|27|1|28]|$A|29|B|2A|1|2B]]|C|$]]|$1|D|3|E|5|6|7|2C|8|@]|9|@$A|2D|B|2E|1|2F]]|C|$]]|$1|F|3|G|5|H|7|2G|8|@$A|2H|B|2I|I|J]|$A|2J|B|2K|I|K]|$A|2L|B|2M|I|K]|$A|2N|B|2O|I|K]]|9|@$A|2P|B|2Q|1|2R]]|C|$]]|$1|L|3|M|5|N|7|2S|8|@]|9|@]|C|$]]|$1|O|3|P|5|N|7|2T|8|@$A|2U|B|2V|I|K]|$A|2W|B|2X|I|K]|$A|2Y|B|2Z|I|K]]|9|@]|C|$]]|$1|Q|3|R|5|6|7|30|8|@$A|31|B|32|I|K]]|9|@]|C|$]]|$1|S|3|T|5|6|7|33|8|@]|9|@]|C|$]]|$1|U|3|V|5|6|7|34|8|@$A|35|B|36|I|K]]|9|@]|C|$]]|$1|W|3|X|5|N|7|37|8|@]|9|@$A|38|B|39|1|3A]]|C|$]]|$1|Y|3|Z|5|6|7|3B|8|@$A|3C|B|3D|I|K]]|9|@]|C|$]]|$1|10|3|11|5|N|7|3E|8|@]|9|@]|C|$]]|$1|12|3|13|5|6|7|3F|8|@$A|3G|B|3H|I|K]]|9|@]|C|$]]|$1|14|3|15|5|N|7|3I|8|@$A|3J|B|3K|I|K]|$A|3L|B|3M|I|K]]|9|@]|C|$]]|$1|16|3|17|5|N|7|3N|8|@]|9|@]|C|$]]|$1|18|3|19|5|6|7|3O|8|@$A|3P|B|3Q|I|K]]|9|@]|C|$]]|$1|1A|3|1B|5|N|7|3R|8|@]|9|@]|C|$]]|$1|1C|3|1D|5|6|7|3S|8|@$A|3T|B|3U|I|K]]|9|@]|C|$]]|$1|1E|3|1F|5|N|7|3V|8|@$A|3W|B|3X|I|K]|$A|3Y|B|3Z|I|K]]|9|@]|C|$]]|$1|1G|3|1H|5|6|7|40|8|@]|9|@$A|41|B|42|1|43]]|C|$]]|$1|1I|3|1J|5|6|7|44|8|@]|9|@]|C|$]]|$1|1K|3|1L|5|1M|7|45|8|@]|9|@$A|46|B|47|1|48]]|C|$]]|$1|1N|3|-4|5|6|7|49|8|@]|9|@]|C|$]]]|1O|$1P|$5|1Q|1R|1S|C|$1T|1U]]|1V|$5|1Q|1R|1S|C|$1T|1W]]|1X|$5|1Q|1R|1S|C|$1T|1U]]|1Y|$5|1Q|1R|1S|C|$1T|1Z]]|20|$5|1Q|1R|1S|C|$1T|21]]|22|$5|1Q|1R|1S|C|$1T|23]]|24|$5|1Q|1R|1S|C|$1T|1L]]]]

There seems to be a <a href="https://github.com/git-for-windows/git/wiki/Install-inside-MSYS2-proper" rel="nofollow noreferrer">documented way</a> to do this without having to install the Git for Windows SDK (which is very large). I was given the link to this info by PhilipOakley when I asked about all this on GitHub <a href="https://github.com/git-for-windows/git/issues/1912" rel="nofollow noreferrer">issue #1912</a>.
Here's the current text of the Git for Windows GitHub <a href="https://github.com/git-for-windows/git/wiki/Install-inside-MSYS2-proper" rel="nofollow noreferrer">wiki page</a> about it:
<blockquote>
##Install inside MSYS2 proper
###Please note that this scenario is not officially supported by Git for Windows
(The reason this is unsupported is that there are no volunteers to support that scenario.)
This guide assumes that you want the 64-bit version of Git for Windows.
Git for Windows being based on MSYS2, it's possible to install the <code>git</code> package into an existing MSYS2 installation. That means that if you are already using MSYS2 on your computer, you can use Git for Windows without running the full installer or using the portable version.
Note however that there are some caveats for going this way. Git for Windows created some patches for <code>msys2-runtime</code> that have not been sent upstream. (This had been planned, but it was determined in issue <a href="https://github.com/git-for-windows/git/issues/284" rel="nofollow noreferrer">#284</a> that it would probably not be happening.) This means that you have to install Git for Windows customized <code>msys2-runtime</code> to have a fully working git inside MSYS2.
Here the steps to take:
<ol>
<li>Open an MSYS2 terminal.
</li>
<li>Edit <code>/etc/pacman.conf</code> and just before <code>[mingw32]</code> (line #71 on my machine), add the <code>git-for-windows</code> packages repository:
</li>
</ol>
<code>[git-for-windows] Server = https://wingit.blob.core.windows.net/x86-64</code>
and optionally also the MINGW-only repository for the opposite architecture (i.e. MINGW32 for 64-bit SDK):
<code>[git-for-windows-mingw32] Server = https://wingit.blob.core.windows.net/i686</code>
<ol start="3">
<li>Authorize signing key (this step may have to be repeated occasionally until <a href="https://github.com/msys2/msys2/issues/62" rel="nofollow noreferrer">https://github.com/msys2/msys2/issues/62</a> is fixed)</li>
</ol>
<code>curl -L https://raw.githubusercontent.com/git-for-windows/build-extra/master/git-for-windows-keyring/git-for-windows.gpg | pacman-key --add - &amp;&amp; pacman-key --lsign-key 1A9F3986</code>
<ol start="4">
<li>Then synchronize new repository</li>
</ol>
<code>pacboy update</code>
<ol start="5">
<li>This updates <code>msys2-runtime</code> and therefore will ask you to close the window (not just exit the pacman process). Don't panic, simply close all currently open MSYS2 shells and MSYS2 programs. Double-check Task Manager and kill <code>pacman.exe</code> it's still running after the window is closed, because it can linger. Once all are closed, start a new terminal again.
</li>
<li>Then synchronize again (updating the non-core part of the packages):
</li>
</ol>
<code>pacboy update</code>
<ol start="7">
<li>And finally install the Git/cURL packages:</li>
</ol>
<code>pacboy sync git:x git-doc-html:x git-doc-man:x git-extra: curl:x</code>
<ol start="8">
<li>Finally, check that everything went well by doing <code>git --version</code> in a MINGW64 shell and it should output something like <code>git version 2.14.1.windows.1</code> (or newer).</li>
</ol>
</blockquote>
@VonC pointed out in the comments that there is discussion about possible additional steps needed in this approach, around half-way down the discussion at <a href="https://github.com/git-for-windows/git/issues/2688" rel="nofollow noreferrer">https://github.com/git-for-windows/git/issues/2688</a>.
And now, potentially a new way to achieve the required result too:
<ul>
<li><a href="https://github.com/git-for-windows/git/issues/2688#issuecomment-772311418" rel="nofollow noreferrer">https://github.com/git-for-windows/git/issues/2688#issuecomment-772311418</a></li>
</ul>

blocks|key|1504076|text|我不想离开我已经在工作的Windows安装Git，所以我临时做了一些：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1504077|在其他地方安装。为此您将需要超过3GB的空闲空间。|ordered-list-item|1504078|将${git-sdk}/usr/bin/pacman.exe复制到${git}/usr/bin|offset|length|style|CODE|1504079|将${git-sdk}/etc/pacman.conf和${git-sdk}/etc/pacman.d复制到${git}/etc|1504080|将${git-sdk}/var复制到${git}/|1504081|就这样。现在您可以打开Git并运行pacman+-S+python在现有的Git安装程序上安装软件包。|1504082|您将需要对Git进行Windows目录的写访问。而且，您的pacman现在认为它已经安装了许多软件包(来自SDK)，但它并没有阻止我使用它。|1504083|entityMap^0|0|0|1|T|X|E|0|1|Q|S|N|1I|A|0|1|E|I|7|0|H|G|0|T|6|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|W|8|@$G|X|H|Y|I|J]|$G|Z|H|10|I|J]]|9|@]|A|$]]|$1|K|3|L|5|D|7|11|8|@$G|12|H|13|I|J]|$G|14|H|15|I|J]|$G|16|H|17|I|J]]|9|@]|A|$]]|$1|M|3|N|5|D|7|18|8|@$G|19|H|1A|I|J]|$G|1B|H|1C|I|J]]|9|@]|A|$]]|$1|O|3|P|5|6|7|1D|8|@$G|1E|H|1F|I|J]]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1G|8|@$G|1H|H|1I|I|J]]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|T|$]]

I did not want to move from my already working Git for Windows installation so I improvised a bit:

<ol>
<li>Install Git for Windows SDK somewhere else. You'll need more than 3 GB of free space for that.</li>
<li>Copy <code>${git-sdk}/usr/bin/pacman.exe</code> to <code>${git}/usr/bin</code></li>
<li>Copy <code>${git-sdk}/etc/pacman.conf</code> and <code>${git-sdk}/etc/pacman.d</code> to <code>${git}/etc</code></li>
<li>Copy <code>${git-sdk}/var</code> to <code>${git}/</code></li>
</ol>

That's all. You can now open your Git Bash and run <code>pacman -S python</code> to install packages on your existing Git for Windows setup.

You will need write access to Git for Windows directory. Also, your <code>pacman</code> now thinks it has a lot of packages installed (from SDK) but it did not stop me from using it.

blocks|key|337983|text|在msys2+20190524上进行测试，x86_64+1909+10.0.18363.752和msys2+20220128在Windows+11+x86_64+21H2+10.0.22000.434上测试|type|unstyled|depth|inlineStyleRanges|entityRanges|data|337984|在Windows中使用常规的Git。|337985|安装msys2+(测试版本20190524+)。或Git+for+Windows+SDK.(没有经过充分测试，但应该有效。)两者都包括PacMan和Git。|ordered-list-item|offset|length|style|CODE|337986|将VFS用于Git+for+Windows或Scalar+for+Git+for+Windows+(也称为Microsoft+git)。方法1(有一些限制)|337987|安装VFSForGit+(+https://github.com/microsoft/VFSForGit+)。|337988|安装Microsoft+(+https://github.com/microsoft/git+)时，启用此选项“从命令行和第三方软件中安装git”。|337989|在msys64\usr\bin\中创建一个名为"git“的符号链接，指向C:\Program+Files\Git\bin\git.exe。在cmd.exe中执行以下命令，而不是在bash中。mklink+git+"C:\Program+Files\Git\bin\git.exe"|337990|克隆一个新的gvfs回购。gvfs+clone+https://dev.azure.com/somebody/_git/somerepo。只能在msys2.上执行gvfs命令。|BOLD|337991|通常在msys2上使用git命令。|337992|将VFS用于Git+for+Windows或Scalar用于Git+for+Windows。方法2|337993|用于Git的虚拟文件系统(以前是GVFS+)。官方网站https://vfsforgit.org/是推荐的。对2.22和2.26版本进行了测试。标量(官方网站https://github.com/microsoft/scalar+)是不推荐的，也不是完全测试的。|337994|安装GVFS和Git+for+Windows+with+GVFS+patch。或者安装Scalar+for+Git和Git+for+Windows+with+Scalar+patch。不是同一台机器上的两个。默认的安装目标是C:\Program+Files\Git。|337995|安装msys2+x64而不是C:\Program+Files\Git。默认情况下，它在C:\msys64中。|337996|复制msys2的文件和子文件夹(+/etc和git二进制文件除外)。msys2没有工厂提供的git。)到Git版本，并将/etc/pacman.d和/etc/pacman.conf在msys64文件夹中复制到Git安装文件夹，覆盖现有文件。它将将msys2和MinGW运行时更新为最新版本。对于PacMan，必要的文件是/usr/bin/pac*+;+/etc/pacman.conf+;+/etc/pacman.d/+;+/var+;+/usr/bin/msys*+;。(没有完全测试)。|337997|安装终端应用程序。运行C:\Program+Files\Git\bin\bash.exe将启动Git的bash。Run+C:\Program+Files\Git\usr\bin\bash.exe将启动msys2的bash。为终端程序(如超终端+)配置bash路径。由于Git位于系统文件夹中，所以终端程序应该以管理员的身份运行。|337998|配置$PATH是GVFS的环境变量。在Git+Bash中运行此命令。export+PATH=$PATH:/C/Program\+Files/GVFS或export+PATH=$PATH:"/C/Program+Files/GVFS".或在控制面板的系统属性中为GVFS设置环境变量。重新开始生效。有时这个配置不能工作，但是PacMan仍然可以运行。|337999|修复PacMan。设置二进制文件的可执行权限。狐狸的例子。chmod+%2Bx+/usr/bin/pacman+;+pacman-key+--init+;+pacman-key+--populate+msys2+;+pacman-key+--refresh-keys+;+pacman+--sync+pacman+--refresh+--sysupgrade+--sysupgrade+--overwrite+"*"。使用--overwrite+\*选项，因为一些包是由Git而不是PacMan安装的。|338000|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/microsoft/VFSForGit|1|https://github.com/microsoft/git|2|https://vfsforgit.org/|3|https://github.com/microsoft/scalar|4|https://hyper.is/^0|0|0|2|5|P|J|0|0|E|12|0|0|E|W|1|0|1|F|10|W|2N|19|0|D|1J|1X|9|0|0|0|39|4|R|M|2|27|Z|3|0|2|4|7|V|17|E|1M|X|34|K|2K|B|0|E|K|17|9|0|1O|D|22|G|4G|23|0|B|X|1O|11|3A|3|4|0|Y|14|23|15|0|T|4X|5T|E|0^^$0|@$1|2|3|4|5|6|7|1T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1U|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|1V|8|@$G|1W|H|1X|I|J]|$G|1Y|H|1Z|I|J]]|9|@]|A|$]]|$1|K|3|L|5|6|7|20|8|@]|9|@]|A|$]]|$1|M|3|N|5|F|7|21|8|@]|9|@$G|22|H|23|1|24]]|A|$]]|$1|O|3|P|5|F|7|25|8|@]|9|@$G|26|H|27|1|28]]|A|$]]|$1|Q|3|R|5|F|7|29|8|@$G|2A|H|2B|I|J]|$G|2C|H|2D|I|J]|$G|2E|H|2F|I|J]]|9|@]|A|$]]|$1|S|3|T|5|F|7|2G|8|@$G|2H|H|2I|I|J]|$G|2J|H|2K|I|U]]|9|@]|A|$]]|$1|V|3|W|5|F|7|2L|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|2M|8|@]|9|@]|A|$]]|$1|Z|3|10|5|6|7|2N|8|@$G|2O|H|2P|I|U]]|9|@$G|2Q|H|2R|1|2S]|$G|2T|H|2U|1|2V]]|A|$]]|$1|11|3|12|5|F|7|2W|8|@$G|2X|H|2Y|I|J]|$G|2Z|H|30|I|J]|$G|31|H|32|I|J]|$G|33|H|34|I|J]|$G|35|H|36|I|J]|$G|37|H|38|I|U]]|9|@]|A|$]]|$1|13|3|14|5|F|7|39|8|@$G|3A|H|3B|I|J]|$G|3C|H|3D|I|J]]|9|@]|A|$]]|$1|15|3|16|5|F|7|3E|8|@$G|3F|H|3G|I|J]|$G|3H|H|3I|I|J]|$G|3J|H|3K|I|J]]|9|@]|A|$]]|$1|17|3|18|5|F|7|3L|8|@$G|3M|H|3N|I|J]|$G|3O|H|3P|I|J]]|9|@$G|3Q|H|3R|1|3S]]|A|$]]|$1|19|3|1A|5|F|7|3T|8|@$G|3U|H|3V|I|J]|$G|3W|H|3X|I|J]]|9|@]|A|$]]|$1|1B|3|1C|5|F|7|3Y|8|@$G|3Z|H|40|I|J]|$G|41|H|42|I|J]]|9|@]|A|$]]|$1|1D|3|-4|5|6|7|43|8|@]|9|@]|A|$]]]|1E|$1F|$5|1G|1H|1I|A|$1J|1K]]|1L|$5|1G|1H|1I|A|$1J|1M]]|1N|$5|1G|1H|1I|A|$1J|1O]]|1P|$5|1G|1H|1I|A|$1J|1Q]]|1R|$5|1G|1H|1I|A|$1J|1S]]]]

<h3>Tested on msys2 20190524 on Windows 10 x86_64 1909 10.0.18363.752 and msys2 20220128 on Windows 11 x86_64 21H2 10.0.22000.434</h3>
<h3>Using regular Git for Windows.</h3>
<ol>
<li>Install <code>msys2</code> (Version 20190524 is tested.) or <code>Git for Windows SDK</code>. (Not fully tested, but it should work.) Both include PacMan and Git.</li>
</ol>
<h3>Using VFS for Git for Windows or Scalar for Git for Windows (Aka Microsoft git). Method #1 (with some limitations)</h3>
<ol>
<li>Install VFSForGit ( <a href="https://github.com/microsoft/VFSForGit" rel="nofollow noreferrer">https://github.com/microsoft/VFSForGit</a> ).</li>
<li>Install Microsoft git ( <a href="https://github.com/microsoft/git" rel="nofollow noreferrer">https://github.com/microsoft/git</a> ) with this option &quot;Git from the command line and also from 3rd-party software&quot; enabled.</li>
<li>Create a symbolic link named &quot;git&quot; in <code>msys64\usr\bin\</code> pointing to <code>C:\Program Files\Git\bin\git.exe</code> . Execute the following command in cmd.exe, not in bash. <code>mklink git &quot;C:\Program Files\Git\bin\git.exe&quot;</code></li>
<li>Clone a new gvfs repo. <code>gvfs clone https://dev.azure.com/somebody/_git/somerepo</code>. Only the gvfs command can not be executed on msys2.</li>
<li>Use the git command as you are on msys2 normally.</li>
</ol>
<h3>Using VFS for Git for Windows or Scalar for Git for Windows. Method #2</h3>
Virtual Filesystem for Git (formerly was GVFS. Official website <a href="https://vfsforgit.org/" rel="nofollow noreferrer">https://vfsforgit.org/</a> ) is recommended. Version 2.22 &amp; 2.26 are tested. Scalar (Official website <a href="https://github.com/microsoft/scalar" rel="nofollow noreferrer">https://github.com/microsoft/scalar</a> ) is NOT recommended, nor completely tested.
<ol>
<li>Install <code>GVFS</code> and <code>Git for Windows with GVFS patch</code>. Or install <code> Scalar for Git</code> and <code>Git for Windows with Scalar patch</code>. NOT BOTH on the same machine. The default installation destination is <code>C:\Program Files\Git</code>.</li>
<li>Install msys2 x64 somewhere other than <code>C:\Program Files\Git</code>. By default, it is in <code>C:\msys64</code>.</li>
<li>Copy files and subfolders of msys2 (except /etc and git binaries. The msys2 comes without git from factory.) to Git for Windows VFS edition, and copy <code>/etc/pacman.d</code> and <code>/etc/pacman.conf</code> in msys64 folder to Git installation folder, overwrite existing files. It will update msys2 and MinGW runtime to the latest version. For PacMan, the necessary files are <code>/usr/bin/pac* ; /etc/pacman.conf ; /etc/pacman.d/ ; /var ; /usr/bin/msys* ;</code> .(Not fully tested.)</li>
<li>Setup terminal applications. Run <code>C:\Program Files\Git\bin\bash.exe</code> will launch the bash of Git for Windows. Run <code>C:\Program Files\Git\usr\bin\bash.exe</code> will launch bash of msys2. Configure the path of bash for terminal programs, such as <a href="https://hyper.is" rel="nofollow noreferrer">Hyper Terminal</a>. Since Git is in the system folder, terminal programs should be Run as administrator.</li>
<li>Config $PATH the environmental variable for GVFS. Run this command in Git Bash. <code>export PATH=$PATH:/C/Program\ Files/GVFS</code> or <code>export PATH=$PATH:&quot;/C/Program Files/GVFS&quot;</code>. Or set environmental variables for GVFS in the system property of the control panel. Relogin to take effect. Sometimes this configuration does not work, but PacMan can still run.</li>
<li>Fix PacMan. Set executable permission for binaries. Fox example. <code>chmod +x /usr/bin/pacman ; pacman-key --init ; pacman-key --populate msys2 ; pacman-key --refresh-keys ; pacman --sync pacman --refresh --sysupgrade --sysupgrade --overwrite &quot;*&quot; </code> . Use the option <code>--overwrite \*</code> because some packages were installed by Git for Windows instead of PacMan.</li>
</ol>

blocks|key|1504177|text|"Git+for+Windows+SDK“为5.33GB，"Git+for+Windows”为691+to，“便携式Git”为275+to。我用的是精巧又吝啬的便携Git。起初，试图在后两种Git+(msys2)中恢复和使用pacman似乎是没有希望的，因为谷歌排除了/var/lib/pacman/local中的所有元数据文件。请阅读这份官方解释：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1504178|错误|offset|length|1504179|如果没有这些元数据文件，您就不知道谷歌为构建这2种Git版本而选择的msys2包的确切集合和版本。如果您强制安装或复制msys2包的当前版本，则会面临与Google构建和测试的git二进制文件版本不匹配的风险。|1504180|好吧，直到我发现这个文件:+/etc/package-versions.txt，匹配的msys2包和版本的列表。现在在github有一个明确的来源。下面是我如何还原Portable+Git中的pacman：|1504181|步骤1:运行以下命令下载/etc/pacman.conf和3个包：帕克曼、帕克曼镜和msys2+2-键环。这些是在.xz切换到zstd之前的msys2包。见下面我的评论。|1504182|curl+https://raw.githubusercontent.com/msys2/MSYS2-packages/7858ee9c236402adf569ac7cff6beb1f883ab67c/pacman/pacman.conf+-o+/etc/pacman.conf
for+f+in+pacman-5.2.2-4-x86_64+pacman-mirrors-20201028-1-any+msys2-keyring-1~20201002-1-any;+
+do+curl+https://repo.msys2.org/msys/x86_64/$f.pkg.tar.xz+-o+~/Downloads/$f.pkg.tar.xz;
done|code-block|syntax|javascript|1504183|步骤2:在根目录下解压它们，然后用以下命令还原pacman：|1504184|cd+/
tar+x+--xz+-vf+~/Downloads/msys2-keyring-1~20201002-1-any.pkg.tar.xz+usr
tar+x+--xz+-vf+~/Downloads/pacman-mirrors-20201028-1-any.pkg.tar.xz+etc
tar+x+--xz+-vf+~/Downloads/pacman-5.2.2-4-x86_64.pkg.tar.xz+usr
mkdir+-p+/var/lib/pacman
pacman-key+--init
pacman-key+--populate+msys2
pacman+-Syu|1504185|步骤3:下面两个命令恢复所有匹配的元数据。第二个命令是多行的，但仍然可以安全地剪切和粘贴(要耐心)：|1504186|URL=https://github.com/git-for-windows/git-sdk-64/raw/main
cat+/etc/package-versions.txt+%7C+while+read+p+v;+do+d=/var/lib/pacman/local/$p-$v;
+mkdir+-p+$d;+echo+$d;+for+f+in+desc+files+install+mtree;+do+curl+-sSL+"$URL$d/$f"+-o+$d/$f;
+done;+done|1504187|第四步:现在，要求“make”和“zip”是不是太过分了？|1504188|pacman+-S+make+zip|1504189|哇，仍然只是一个337à意味着小环境，可以扩展和升级！|1504190|entityMap|0|LINK|mutability|MUTABLE|url|https://wiki.archlinux.org/index.php/Pacman#.22Failed_to_commit_transaction_.28conflicting_files.29.22_error|1|https://repo.msys2.org/msys/x86_64/pacman-5.2.2-4-x86_64.pkg.tar.xz|2|https://repo.msys2.org/msys/x86_64/pacman-mirrors-20201028-1-any.pkg.tar.xz|3|https://repo.msys2.org/msys/x86_64/msys2-keyring-1%257E20201002-1-any.pkg.tar.xz^0|0|0|2|0|0|0|0|X|3|1|11|4|2|16|A|3|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1J|8|@]|9|@$D|1K|E|1L|1|1M]]|A|$]]|$1|F|3|G|5|6|7|1N|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|1O|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1P|8|@]|9|@$D|1Q|E|1R|1|1S]|$D|1T|E|1U|1|1V]|$D|1W|E|1X|1|1Y]]|A|$]]|$1|L|3|M|5|N|7|1Z|8|@]|9|@]|A|$O|P]]|$1|Q|3|R|5|6|7|20|8|@]|9|@]|A|$]]|$1|S|3|T|5|N|7|21|8|@]|9|@]|A|$O|P]]|$1|U|3|V|5|6|7|22|8|@]|9|@]|A|$]]|$1|W|3|X|5|N|7|23|8|@]|9|@]|A|$O|P]]|$1|Y|3|Z|5|6|7|24|8|@]|9|@]|A|$]]|$1|10|3|11|5|N|7|25|8|@]|9|@]|A|$O|P]]|$1|12|3|13|5|6|7|26|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|27|8|@]|9|@]|A|$]]]|15|$16|$5|17|18|19|A|$1A|1B]]|1C|$5|17|18|19|A|$1A|1D]]|1E|$5|17|18|19|A|$1A|1F]]|1G|$5|17|18|19|A|$1A|1H]]]]

&quot;Git for Windows SDK&quot; is 5.33GB compared to &quot;Git for Windows&quot; 691MB compared to &quot;Portable Git&quot; 275MB. I use the lean and mean Portable Git. At first, it seems hopeless trying to restore and use pacman in the latter two flavors of Git (msys2), because Google excluded ALL metadata files in /var/lib/pacman/local. Please read this official explanation:
<a href="https://wiki.archlinux.org/index.php/Pacman#.22Failed_to_commit_transaction_.28conflicting_files.29.22_error" rel="noreferrer">https://wiki.archlinux.org/index.php/Pacman#.22Failed_to_commit_transaction_.28conflicting_files.29.22_error</a>
Without those metadata files, you don't know the exact collection and version of the msys2 packages Google selected to build a release of those 2 flavors of Git. If you force to install or copy the current version of msys2 packages, you run the risk of version mismatch with git binaries Google built and tested.
Well, that's until I discover this file: /etc/package-versions.txt, the laundry list of matching msys2 packages and versions. Now there is a definitive source in github. Here is how I restore pacman in Portable Git:
Step 1: Run these commands to download /etc/pacman.conf and 3 packages: <a href="https://repo.msys2.org/msys/x86_64/pacman-5.2.2-4-x86_64.pkg.tar.xz" rel="noreferrer">pacman</a>, <a href="https://repo.msys2.org/msys/x86_64/pacman-mirrors-20201028-1-any.pkg.tar.xz" rel="noreferrer">pacman-mirrors</a> and <a href="https://repo.msys2.org/msys/x86_64/msys2-keyring-1%7E20201002-1-any.pkg.tar.xz" rel="noreferrer">msys2-keyring</a>. These are .xz packages before msys2 switched to zstd. See my comment below.
<pre><code>curl https://raw.githubusercontent.com/msys2/MSYS2-packages/7858ee9c236402adf569ac7cff6beb1f883ab67c/pacman/pacman.conf -o /etc/pacman.conf
for f in pacman-5.2.2-4-x86_64 pacman-mirrors-20201028-1-any msys2-keyring-1~20201002-1-any; 
 do curl https://repo.msys2.org/msys/x86_64/$f.pkg.tar.xz -o ~/Downloads/$f.pkg.tar.xz;
done
</code></pre>
Step 2: Unpack them at the root then restore pacman with these commands:
<pre><code>cd /
tar x --xz -vf ~/Downloads/msys2-keyring-1~20201002-1-any.pkg.tar.xz usr
tar x --xz -vf ~/Downloads/pacman-mirrors-20201028-1-any.pkg.tar.xz etc
tar x --xz -vf ~/Downloads/pacman-5.2.2-4-x86_64.pkg.tar.xz usr
mkdir -p /var/lib/pacman
pacman-key --init
pacman-key --populate msys2
pacman -Syu
</code></pre>
Step 3: The next two commands restore all matching metadata. The second command is multi-line but still safe to cut and paste (be patient):
<pre><code>URL=https://github.com/git-for-windows/git-sdk-64/raw/main
cat /etc/package-versions.txt | while read p v; do d=/var/lib/pacman/local/$p-$v;
 mkdir -p $d; echo $d; for f in desc files install mtree; do curl -sSL &quot;$URL$d/$f&quot; -o $d/$f;
 done; done
</code></pre>
Step 4: Now, is it too much to ask for 'make' and 'zip'?
<pre><code>pacman -S make zip
</code></pre>
Voilà, still just a 337MB mean little environment that can expand and upgrade!

blocks|key|338046|text|从msys2中复制pacman对我有用，最后大多数人忘记了您可以使用pacman作为pacman+-Syy+msys/pacman进行自我更新|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|338047|在msys+pacman+-Ql+pacman中运行|ordered-list-item|338048|复制列出的匹配文件|338049|/etc/*.|unordered-list-item|338050|/usr/bin|338051|/usr/包括|338052|/usr/lib|338053|/var/lib|338054|以及复制数据库|338055|/etc/pacman|338056|此时，我已经有了一个工作的pacman，我用pacman+-Ss+pacman检查它，但是缺少文件，所以我运行了自刷新pacman+-Syy+msys/pacman。|338057|entityMap^0|16|N|0|6|H|0|0|0|0|0|0|0|0|0|M|H|1N|N|0^^$0|@$1|2|3|4|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|16|8|@$9|17|A|18|B|C]]|D|@]|E|$]]|$1|I|3|J|5|H|7|19|8|@]|D|@]|E|$]]|$1|K|3|L|5|M|7|1A|8|@]|D|@]|E|$]]|$1|N|3|O|5|M|7|1B|8|@]|D|@]|E|$]]|$1|P|3|Q|5|M|7|1C|8|@]|D|@]|E|$]]|$1|R|3|S|5|M|7|1D|8|@]|D|@]|E|$]]|$1|T|3|U|5|M|7|1E|8|@]|D|@]|E|$]]|$1|V|3|W|5|H|7|1F|8|@]|D|@]|E|$]]|$1|X|3|Y|5|M|7|1G|8|@]|D|@]|E|$]]|$1|Z|3|10|5|H|7|1H|8|@$9|1I|A|1J|B|C]|$9|1K|A|1L|B|C]]|D|@]|E|$]]|$1|11|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]]|12|$]]

Copying pacman from msys2 works for me, at the end most people forget that you can use pacman for self update as <code>pacman -Syy msys/pacman</code>
<ol>
<li>Run in msys <code>pacman -Ql pacman</code>
</li>
<li>Copy files listed that match
</li>
</ol>
<ul>
<li>/etc/*.conf</li>
<li>/usr/bin</li>
<li>/usr/include</li>
<li>/usr/lib</li>
<li>/var/lib</li>
</ul>
<ol start="3">
<li>And copy databases as well</li>
</ol>
<ul>
<li>/etc/pacman</li>
</ul>
<ol start="4">
<li>At this point I already have a working pacman,I check it with <code>pacman -Ss pacman</code> but there are missing files so I run self refresh
<code>pacman -Syy msys/pacman</code></li>
</ol>

blocks|key|952957|text|现在使用zstd压缩pacman。所以更新了@michael-chen的场景(我使用wsl的unzstd)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|952958|for+f+in+pacman-6.0.1-25-x86_64.pkg.tar.zst+pacman-mirrors-20221016-1-any.pkg.tar.zst+msys2-keyring-1~20221024-1-any.pkg.tar.zst;+++do+curl+https://repo.msys2.org/msys/x86_64/$f+-o+~/Downloads/$f;+done
cd+/
tar+--use-compress-program=unzstd+-xvf+~/Downloads/msys2-keyring-1~20221024-1-any.pkg.tar.zst+usr
tar+--use-compress-program=unzstd+-xvf+~/Downloads/pacman-mirrors-20221016-1-any.pkg.tar.zst+etc
tar+--use-compress-program=unzstd+-xvf+~/Downloads/pacman-6.0.1-25-x86_64.pkg.tar.zst+usr
mkdir+-p+/var/lib/pacman
pacman-key+--init
pacman-key+--populate+msys2
pacman+-Sy
export+URL=https://github.com/git-for-windows/git-sdk-64/raw/main
cat+/etc/package-versions.txt+%7C+while+read+p+v;+do+d=/var/lib/pacman/local/$p-$v;+mkdir+-p+$d;+echo+$d;+for+f+in+desc+files+install+mtree;+do+curl+-sSL+"$URL$d/$f"+-o+$d/$f;+done;+done|code-block|syntax|javascript|952959|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

pacman is compressed using zstd now.
So updated @michael-chen 's scenario (i use wsl's unzstd):
<pre><code>for f in pacman-6.0.1-25-x86_64.pkg.tar.zst pacman-mirrors-20221016-1-any.pkg.tar.zst msys2-keyring-1~20221024-1-any.pkg.tar.zst; do curl https://repo.msys2.org/msys/x86_64/$f -o ~/Downloads/$f; done
cd /
tar --use-compress-program=unzstd -xvf ~/Downloads/msys2-keyring-1~20221024-1-any.pkg.tar.zst usr
tar --use-compress-program=unzstd -xvf ~/Downloads/pacman-mirrors-20221016-1-any.pkg.tar.zst etc
tar --use-compress-program=unzstd -xvf ~/Downloads/pacman-6.0.1-25-x86_64.pkg.tar.zst usr
mkdir -p /var/lib/pacman
pacman-key --init
pacman-key --populate msys2
pacman -Sy
export URL=https://github.com/git-for-windows/git-sdk-64/raw/main
cat /etc/package-versions.txt | while read p v; do d=/var/lib/pacman/local/$p-$v; mkdir -p $d; echo $d; for f in desc files install mtree; do curl -sSL &quot;$URL$d/$f&quot; -o $d/$f; done; done
</code></pre>

I'm reading the github wiki for git-for-windows and it says that msys2 bundles pacman: <a href="https://github.com/git-for-windows/git/wiki/Package-management" rel="noreferrer">https://github.com/git-for-windows/git/wiki/Package-management</a>
But when I invoke it I get:
<pre><code>$ pacman
bash: pacman: command not found
</code></pre>
Does anyone have an idea what is going on?
Which git version does this wiki refer to?
Is there a way to install additional packages to msys2 inside Git for windows?

Package management in Git for Windows (Git Bash)?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在阅读github的github的github wiki，上面写着msys2 bundle pacman：但当我调用它时，我得到：$ pacmanbash: pacman: command not found有人知道这是怎么回事吗？这个wiki指的是哪个git版本？是否有一种方法可以在中安装附加的msys2包？

问Git for Windows (Git Bash)中的包管理？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Git for Windows (Git Bash)中的包管理？EN