Send patches - preferably formatted by git format-patch - to patches at archlinux32 dot org.
summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/index.asciidoc22
-rw-r--r--doc/submitting-patches.asciidoc2
-rw-r--r--doc/translation-help.asciidoc8
3 files changed, 15 insertions, 17 deletions
diff --git a/doc/index.asciidoc b/doc/index.asciidoc
index fa7444db..35de0b90 100644
--- a/doc/index.asciidoc
+++ b/doc/index.asciidoc
@@ -59,11 +59,11 @@ configuration files dealing with pacman.
Changelog
~~~~~~~~~
For a good idea of what is going on in pacman development, take a look at the
-link:https://projects.archlinux.org/pacman.git/[Git summary page] for the
+link:https://git.archlinux.org/pacman.git/[Git summary page] for the
project.
See the most recent
-link:https://projects.archlinux.org/pacman.git/tree/NEWS[NEWS]
+link:https://git.archlinux.org/pacman.git/tree/NEWS[NEWS]
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.
@@ -203,8 +203,8 @@ Development
Mailing List
~~~~~~~~~~~~
There is a mailing list devoted to pacman development, hosted by Arch Linux.
-link:https://mailman.archlinux.org/mailman/listinfo/pacman-dev/[Subscribe] or
-link:https://mailman.archlinux.org/pipermail/pacman-dev/[view the archives].
+link:https://lists.archlinux.org/listinfo/pacman-dev/[Subscribe] or
+link:https://lists.archlinux.org/pipermail/pacman-dev/[view the archives].
Source Code
~~~~~~~~~~~
@@ -215,11 +215,11 @@ these trees).
The current development tree can be fetched with the following command:
- git clone git://projects.archlinux.org/pacman.git pacman
+ git clone git://git.archlinux.org/pacman.git pacman
which will fetch the full development history into a directory named pacman.
You can browse the source as well using
-link:https://projects.archlinux.org/pacman.git/[cgit]. HTTP/HTTPS URLs are also
+link:https://git.archlinux.org/pacman.git/[cgit]. HTTP/HTTPS URLs are also
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
@@ -238,15 +238,13 @@ Although the package manager itself is quite simple, many scripts have been
developed that help automate building and installing packages. These are used
extensively in link:https://www.archlinux.org/[Arch Linux]. Most of these utilities
are available in the Arch Linux projects
-link:https://projects.archlinux.org/[code browser].
+link:https://git.archlinux.org/[code browser].
Utilities available:
-* link:https://projects.archlinux.org/abs.git/[abs] - ABS (Arch Build System), scripts to download & use the Arch Linux PKGBUILD tree
-* link:https://projects.archlinux.org/dbscripts.git/[dbscripts] - scripts used by Arch Linux to manage the main package repositories
-* link:https://projects.archlinux.org/devtools.git/[devtools] - tools to assist in packaging and dependency checking
-* link:https://projects.archlinux.org/namcap.git/[namcap] - a package analysis utility written in python
-* link:https://projects.archlinux.org/srcpac.git/[srcpac] - a bash build-from-source pacman wrapper
+* link:https://git.archlinux.org/dbscripts.git/[dbscripts] - scripts used by Arch Linux to manage the main package repositories
+* link:https://git.archlinux.org/devtools.git/[devtools] - tools to assist in packaging and dependency checking
+* link:https://git.archlinux.org/namcap.git/[namcap] - a package analysis utility written in python
Bugs
----
diff --git a/doc/submitting-patches.asciidoc b/doc/submitting-patches.asciidoc
index 9cf8dc64..88b58ca5 100644
--- a/doc/submitting-patches.asciidoc
+++ b/doc/submitting-patches.asciidoc
@@ -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:
- git clone git://projects.archlinux.org/pacman.git
+ git clone git://git.archlinux.org/pacman.git
Creating your patch
diff --git a/doc/translation-help.asciidoc b/doc/translation-help.asciidoc
index 67117bcc..5a67a2d6 100644
--- a/doc/translation-help.asciidoc
+++ b/doc/translation-help.asciidoc
@@ -4,10 +4,10 @@ Pacman - Translating
This document is here to guide you in helping translate pacman messages,
libalpm messages, and the manual pages for the entire pacman package.
-We are currently using http://www.transifex.com/[Transifex] as the translation
+We are currently using https://www.transifex.com/[Transifex] as the translation
platform for pacman and libalpm. You will need to sign up for an account there
and then register with a translation team on the
-http://www.transifex.com/projects/p/archlinux-pacman/[pacman project page].
+https://www.transifex.com/projects/p/archlinux-pacman/[pacman project page].
NOTE: This may be old information due to our switch to Transifex, but the
gettext website is a very useful guide to read before embarking on translation
@@ -31,7 +31,7 @@ either be hand-edited, or modified with a tool such as poedit, gtranslator or
kbabel. Using a translation tool tends to make the job easier.
Please read up on Transifex usage using the
-http://docs.transifex.com/[Transifex Help] if you are not familiar.
+https://docs.transifex.com/[Transifex Help] if you are not familiar.
Transifex provides a command-line client to help with translations. Here is
an example set of commands if you have a source code checkout and are not
@@ -78,7 +78,7 @@ Incremental Updates
If you have more advanced needs you will have to get a copy of the pacman
repository.
- git clone git://projects.archlinux.org/pacman.git pacman
+ git clone git://git.archlinux.org/pacman.git pacman
Next, you will need to run `./autogen.sh` and `./configure` in the base
directory to generate the correct Makefiles. At this point, all necessary