Send patches - preferably formatted by git format-patch - to patches at archlinux32 dot org.
summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJason St. John <jstjohn@purdue.edu>2013-03-13 22:18:59 -0400
committerAllan McRae <allan@archlinux.org>2013-03-15 13:21:32 +1000
commit9cd344fb0d9b51125e6e18fb90d6d818c5952b0d (patch)
tree851f3ca20a56e185535b38767e2bfc1be36ebaa2 /doc
parentb2ea5f6860dda8267cc7468e975b073be5321228 (diff)
Update documentation to use https links for sites that support it
The Arch web site now redirects to https links for all subdomains, so it makes sense to use these links in the docs for pacman. Links were changed to use https for a couple other sites that support it as well, such as gnu.org and kernel.org. Signed-off-by: Jason St. John <jstjohn@purdue.edu> Signed-off-by: Allan McRae <allan@archlinux.org>
Diffstat (limited to 'doc')
-rw-r--r--doc/PKGBUILD-example.txt2
-rw-r--r--doc/footer.txt2
-rw-r--r--doc/index.txt24
-rw-r--r--doc/submitting-patches.txt4
-rw-r--r--doc/translation-help.txt4
5 files changed, 18 insertions, 18 deletions
diff --git a/doc/PKGBUILD-example.txt b/doc/PKGBUILD-example.txt
index 238c0f40..9ab5dff9 100644
--- a/doc/PKGBUILD-example.txt
+++ b/doc/PKGBUILD-example.txt
@@ -5,7 +5,7 @@ pkgver=2.5.4
pkgrel=3
pkgdesc="A utility to apply patch files to original sources"
arch=('i686' 'x86_64')
-url="http://www.gnu.org/software/patch/patch.html"
+url="https://www.gnu.org/software/patch/patch.html"
license=('GPL')
groups=('base-devel')
depends=('glibc' 'ed')
diff --git a/doc/footer.txt b/doc/footer.txt
index 10ef067f..ccb931ce 100644
--- a/doc/footer.txt
+++ b/doc/footer.txt
@@ -2,7 +2,7 @@
vim:set ts=4 sw=4 syntax=asciidoc noet spell spelllang=en_us:
/////
-See the pacman website at http://www.archlinux.org/pacman/[] for current
+See the pacman website at https://www.archlinux.org/pacman/[] for current
information on pacman and its related tools.
diff --git a/doc/index.txt b/doc/index.txt
index a7a82d42..8f1e17d1 100644
--- a/doc/index.txt
+++ b/doc/index.txt
@@ -53,11 +53,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:http://projects.archlinux.org/pacman.git/[Git summary page] for the
+link:https://projects.archlinux.org/pacman.git/[Git summary page] for the
project.
See the most recent
-link:http://projects.archlinux.org/pacman.git/tree/NEWS[NEWS]
+link:https://projects.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.
@@ -185,8 +185,8 @@ Development
Mailing List
~~~~~~~~~~~~
There is a mailing list devoted to pacman development, hosted by Arch Linux.
-link:http://mailman.archlinux.org/mailman/listinfo/pacman-dev/[Subscribe] or
-link:http://mailman.archlinux.org/pipermail/pacman-dev/[view the archives].
+link:https://mailman.archlinux.org/mailman/listinfo/pacman-dev/[Subscribe] or
+link:https://mailman.archlinux.org/pipermail/pacman-dev/[view the archives].
Source Code
~~~~~~~~~~~
@@ -201,7 +201,7 @@ The current development tree can be fetched with the following command:
which will fetch the full development history into a directory named pacman.
You can browse the source as well using
-link:http://projects.archlinux.org/pacman.git/[cgit]. HTTP/HTTPS URLs are also
+link:https://projects.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
@@ -218,17 +218,17 @@ Other Utilities
~~~~~~~~~~~~~~~
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:http://www.archlinux.org/[Arch Linux]. Most of these utilities
+extensively in link:https://www.archlinux.org/[Arch Linux]. Most of these utilities
are available in the Arch Linux projects
-link:http://projects.archlinux.org/[code browser].
+link:https://projects.archlinux.org/[code browser].
Utilities available:
-* link:http://projects.archlinux.org/abs.git/[abs] - ABS (Arch Build System), scripts to download & use the Arch Linux PKGBUILD tree
-* link:http://projects.archlinux.org/dbscripts.git/[dbscripts] - scripts used by Arch Linux to manage the main package repositories
-* link:http://projects.archlinux.org/devtools.git/[devtools] - tools to assist in packaging and dependency checking
-* link:http://projects.archlinux.org/namcap.git/[namcap] - a package analysis utility written in python
-* link:http://projects.archlinux.org/srcpac.git/[srcpac] - a bash build-from-source pacman wrapper
+* 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
Bugs
----
diff --git a/doc/submitting-patches.txt b/doc/submitting-patches.txt
index 34287683..d542265c 100644
--- a/doc/submitting-patches.txt
+++ b/doc/submitting-patches.txt
@@ -15,8 +15,8 @@ Patches need to be submitted in GIT format and are best if they are against the
latest version of the code. There are several helpful tutorials for getting
started with GIT if you have not worked with it before.
-* http://www.kernel.org/pub/software/scm/git/docs/gittutorial.html
-* http://wiki.archlinux.org/index.php/Super_Quick_Git_Guide
+* https://www.kernel.org/pub/software/scm/git/docs/gittutorial.html
+* https://wiki.archlinux.org/index.php/Super_Quick_Git_Guide
The pacman code can be fetched using the following command:
diff --git a/doc/translation-help.txt b/doc/translation-help.txt
index ef86dbfe..7b8134e5 100644
--- a/doc/translation-help.txt
+++ b/doc/translation-help.txt
@@ -12,7 +12,7 @@ http://www.transifex.net/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
work, as it describes many of the commands in more detail than I will here:
-http://www.gnu.org/software/gettext/manual/html_node/gettext.html[]. In
+https://www.gnu.org/software/gettext/manual/html_node/gettext.html[]. In
addition, this site presents a small tutorial that I found useful:
http://oriya.sarovar.org/docs/gettext/[].
@@ -155,7 +155,7 @@ source, please contact the pacman-dev mailing list at
mailto:pacman-dev@archlinux.org[].
Some community efforts have been made to translate manpages, and these can be
-found in the link:http://aur.archlinux.org[AUR] (Arch User Repository). Please
+found in the link:https://aur.archlinux.org[AUR] (Arch User Repository). Please
check there first before undergoing a translation effort to ensure you are not
duplicating efforts.