Skip to content

Commit e1ca8c0

Browse files
elieuxdscho
authored andcommitted
Package management: Forget BinTray and manual package uploads
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
1 parent fc53b51 commit e1ca8c0

File tree

1 file changed

+1
-30
lines changed

1 file changed

+1
-30
lines changed

Package-management.md

Lines changed: 1 addition & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -128,33 +128,4 @@ perl -MCPAN -e shell
128128

129129
Pacman repositories are served via HTTP, as static files in a single directory. The most important file in that directory is the *package index*, called `<name>.db.tar.xz` by convention. This package index can be updated via `repo-add <package-index> <package-file>...` (this updated *only* the package index, it does *not* copy the package files into the same directory). Pacman expects to find the package files referenced in the package index in the same directory as the index.
130130

131-
The *Git for Windows*-specific packages are served from Bintray, see [below](#Bintray).
132-
We ship MSYS2 and MinGW packages for two architectures, [`i686`](https://dl.bintray.com/git-for-windows/pacman/i686/) and [`x86_64`](https://dl.bintray.com/git-for-windows/pacman/x86_64/).
133-
134-
## Bintray
135-
136-
[Bintray](https://bintray.com) hosts repositories of binary files, much like GitHub hosts repositories of source files. Git for Windows' binary files are [hosted on Bintray](https://bintray.com/git-for-windows/).
137-
138-
Git for Windows' [most important repository hosted on Bintray](https://bintray.com/git-for-windows/pacman) contains the Pacman repositories [described above](#Repository_structure). The section to add to `pacman.conf` to access this repository is:
139-
140-
```ini
141-
[git-for-windows]
142-
Server = https://dl.bintray.com/$repo/pacman/$arch
143-
SigLevel = Optional
144-
```
145-
146-
## How to upload new versions (*Git for Windows* maintainers only)
147-
148-
To upload new files, a maintainer needs to have permission to write to the `pacman` repository on Bintray. We have a helpful tool in the [`build-extra`](https://github.com/git-for-windows/build-extra) repository to assist in the process, called `pacman-mirror.sh`. After building a new package version (preferably for 32-bit *and* 64-bit), the tool should be used thusly:
149-
150-
```bash
151-
/usr/src/build-extra/pacman-mirror.sh fetch
152-
/usr/src/build-extra/pacman-mirror.sh add \
153-
/path/to/<package>-<version>-i686.pkg.tar.xz \
154-
/path/to/<package>-<version>-x86_64.pkg.tar.xz
155-
/usr/src/build-extra/pacman-mirror.sh push
156-
```
157-
158-
The `fetch` step will initialize or synchronize the local mirror of the Pacman repository, the `add` step will copy the packages into the appropriate location, and the `push` step will update the package index, and upload the packages that are not yet on Bintray as well as the package index.
159-
160-
Note: The `pacman-mirror.sh` tool takes no precaution against simultaneous use. You *will* want to coordinate with your fellow maintainers to avoid running it at the same time as somebody else.
131+
The *Git for Windows*-specific packages are served by [Azure Blob Storage](https://azure.microsoft.com/en-us/services/storage/blobs/), see below. We ship MSYS2 and MINGW packages for two architectures, `i686` and `x86_64`. Pacman is configured to use these in `/etc/pacman.conf`.

0 commit comments

Comments
 (0)