Pacman missing on fresh 2.5.2 install

[so0k]

Context

Got a fresh windows 10 machine, Installed Git-2.5.2-64-bit.exe last Friday. Wanted to install some packages Today - found this package management guide in the wiki, tried to run pacman in git bash:

$  pacman
sh: pacman: command not found

version info:

C:\> ver
Microsoft Windows [Version 10.0.10240]

$ git --version
git version 2.5.2.windows.1

Steps to reproduce the problem

Install git for windows using the setup tools from the git-for-windows website, using mintty shell and try to run pacman... (I'm not using Chocolatey).

I am using ConEmu 150908 64bit

Am I missing something? Also, what are the steps to update git for windows? I couldn't find any documentation for that. Do I have to use chocolatey? (I'd rather not, gave me issues in the past).

[so0k]

to eliminate ConEmu comment, running git bash shortcut created in start menu gives same issue

[nalla]

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 Git for Windows SDK a try.

[so0k]

oh thanks, just found this here: #146

[dscho]

oh thanks, just found this here: #146

Yep. duplicate.

How about contributing an entry in the Frequently Asked Questions?

[so0k]

@dscho - I tried to contribute, is this acceptable?

[dscho]

Very nice! Thanks!

[eric-newton]

Thanks for updating the FAQs, I kept wondering why "pacman" gave me "command not found" when it seemed that everyone else had it...

[shimondoodkin]

maybe somebody could make a script out of this and include it in the distribution
https://stackoverflow.com/questions/32712133/package-management-in-git-for-windows/65204171#65204171

[dscho]

maybe somebody could make a script out of this and include it in the distribution
https://stackoverflow.com/questions/32712133/package-management-in-git-for-windows/65204171#65204171

You really want to make my life as maintainer as miserable as you can possibly make it, don't you?

This is not a supported use case. The reason for that is that it is quite finicky a hack, and unless you really understand the internals of Pacman and Git for Windows' architecture, you are going to shoot yourself in your foot. And then you flock here and complain that it ain't working.

Please do not encourage such a waste of my time.

[zlaski]

We're already building Pacman:

https://github.com/git-for-windows/git-sdk-64/blob/main/usr/bin/pacman.exe

What's preventing us from including this in the installer? Out on the web, it seems that several people have integrated Pacman with Git for Windows without any problems.

As to the "finicky hack", I would gladly take a look if you pointed me in the right direction.

[rimrul]

We're already building Pacman:

I don't think we actually build our own pacman, but rather pick it up from Msys2.

What's preventing us from including this in the installer?

The fact that it would significantly increase the burden of support, while not providing a significant benefit for any intended Git for Windows use case. What advantage would we gain from including pacman in the installer?

As to the "finicky hack", I would gladly take a look if you pointed me in the right direction.

Which part of that stack overflow answer does not seem finicky or like a hack to you? They're ignoring the Git for Windows Package databases and repositories, so all those pacakges will drift apart from what a proper Git for Windows install would include. They're also ignoring the whole git-extra situation.

There are at least three different ways in wich the setup instructions could stop working at any point in the future.

I've probably missed a few issues with that, but it's certainly both finicky and a hack.