I want to take a quick minute to explain a little bit about Pacboy because Hugar brought a user's installation issues to my attention over Discord. You can consider this post to be a sort of technical explanation and not really an announcement, but I want to try to clarify this for everybody and not just the one person.
The user was having a problem installing git using Pacboy because I forgot a colon on the install page for Windows. The git
package in MSYS2 is actually what's called a "virtual" package.https://github.com/msys2/msys2/wiki/Using-packages#installing-a-package
Because the package is virtual, when you install it with Pacman, you only need to specify git
without any x86_64
suffix. Now what Pacboy is, is it's a bash script written by the MSYS2 people that makes it easier to install Pacman packages so you don't have to specify the long package suffixes.https://github.com/msys2/msys2/wiki/Using-packages#avoiding-writing-long-package-names
Long story short, with Pacboy the :x
is for x86_64 (64 bit) and :i
is for i686 (32 bit) just as our instructions said before, but a plain :
after the package name, like git:
, should be used for virtual packages.
Copyright (C) 2015, 2016 Renato Silva
Licensed under BSD
This is a pacman wrapper for MSYS2 which handles the package prefixes
automatically, and provides human-friendly commands for common tasks.
pacboy [command] [arguments]
Arguments will be passed to pacman or pkgfile after translation:
For 64-bit MSYS2, name:i means i686-only
For 64-bit MSYS2, name:x means x86_64-only
For MSYS shell, name:m means mingw-w64
For all shells, name: disables any translation for name
For all shells, repository::name means repository/name
I've updated our Windows installation instructions to clarify all of this.https://enigma-dev.org/docs/wiki/index.php?title=Install%3AWindows&action=historysubmit&diff=31845&oldid=31833