Update broken links pointing to git.archlinux.org

All of these links are broken since the recent move to
gitlab.archlinux.org.

A few projects are, apparently, only available on GitHub, so I've linked
to that source (hopefully that's only temporary).

For git-clone URLs, I've opted for the https URLs since those can be
used by anyone -- whereas the ssh URLs require the user to be registered
on the gitlab instance which is not open to the public yet.

Signed-off-by: Hugo Osvaldo Barrera <hugo@barrera.io>
Signed-off-by: Allan McRae <allan@archlinux.org>
This commit is contained in:
Hugo Osvaldo Barrera 2021-08-14 12:13:28 +02:00 committed by Allan McRae
parent efb714b31c
commit cf923e734b
3 changed files with 7 additions and 8 deletions

View file

@ -59,11 +59,11 @@ configuration files dealing with pacman.
Changelog Changelog
~~~~~~~~~ ~~~~~~~~~
For a good idea of what is going on in pacman development, take a look at the For a good idea of what is going on in pacman development, take a look at the
link:https://git.archlinux.org/pacman.git/[Git summary page] for the link:https://gitlab.archlinux.org/pacman/pacman[Git summary page] for the
project. project.
See the most recent See the most recent
link:https://git.archlinux.org/pacman.git/tree/NEWS[NEWS] link:https://gitlab.archlinux.org/pacman/pacman/-/blob/master/NEWS[NEWS]
file for a not-as-frequently-updated list of changes. However, this should file for a not-as-frequently-updated list of changes. However, this should
contain the biggest changes in a format more concise than the commit log. contain the biggest changes in a format more concise than the commit log.
@ -220,12 +220,11 @@ these trees).
The current development tree can be fetched with the following command: The current development tree can be fetched with the following command:
git clone git://git.archlinux.org/pacman.git pacman git clone https://gitlab.archlinux.org/pacman/pacman.git
which will fetch the full development history into a directory named pacman. which will fetch the full development history into a directory named pacman.
You can browse the source as well using You can browse the source as well using
link:https://git.archlinux.org/pacman.git/[cgit]. HTTP/HTTPS URLs are also link:https://gitlab.archlinux.org/pacman/pacman/[gitlab].
available for cloning purposes; these URLs are listed at the above page.
If you are interested in hacking on pacman, it is highly recommended you join If you are interested in hacking on pacman, it is highly recommended you join
the mailing list mentioned above, as well as take a quick glance at our the mailing list mentioned above, as well as take a quick glance at our
@ -243,7 +242,7 @@ Although the package manager itself is quite simple, many scripts have been
developed that help automate building and installing packages. These are used developed that help automate building and installing packages. These are used
extensively in link:https://archlinux.org/[Arch Linux]. Most of these utilities extensively in link:https://archlinux.org/[Arch Linux]. Most of these utilities
are available in the Arch Linux projects are available in the Arch Linux projects
link:https://git.archlinux.org/[code browser]. link:https://gitlab.archlinux.org/archlinux[code browser].
Utilities available: Utilities available:

View file

@ -20,7 +20,7 @@ started with GIT if you have not worked with it before.
The pacman code can be fetched using the following command: The pacman code can be fetched using the following command:
git clone git://git.archlinux.org/pacman.git git clone https://gitlab.archlinux.org/pacman/pacman.git
Creating your patch Creating your patch

View file

@ -78,7 +78,7 @@ Incremental Updates
If you have more advanced needs you will have to get a copy of the pacman If you have more advanced needs you will have to get a copy of the pacman
repository. repository.
git clone git://git.archlinux.org/pacman.git pacman git clone https://gitlab.archlinux.org/pacman/pacman.git
Next, you will need to run `./autogen.sh` and `./configure` in the base Next, you will need to run `./autogen.sh` and `./configure` in the base
directory to generate the correct Makefiles. At this point, all necessary directory to generate the correct Makefiles. At this point, all necessary