summaryrefslogtreecommitdiff
path: root/doc/lispref/package.texi
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2019-09-22 23:53:39 -0700
committerPaul Eggert <eggert@cs.ucla.edu>2019-09-23 00:12:52 -0700
commit946a56a10fed769646a8b7c4ebc53f53c84be896 (patch)
tree33a93593b428789b7e49376427eac09d21082808 /doc/lispref/package.texi
parent78669517dc3db4d6d51fb26d71073fc0c196ab5d (diff)
downloademacs-946a56a10fed769646a8b7c4ebc53f53c84be896.tar.gz
Update some URLs
This mostly changes http: to https: in URLs. It also updates some URLs that have moved, removes some URLs that no longer work, recommends against using procmail (procmail.org no longer works), and removes some mentions of the no-longer-existing Gmane, LPF and VTW. It doesn't update all URLs, just the ones I had time for. * GNUmakefile (help): * admin/admin.el (manual-doctype-string): * admin/charsets/Makefile.in (${charsetdir}/ALTERNATIVNYJ.map): * admin/charsets/mapconv: * lisp/net/soap-client.el (soap-create-envelope): * lisp/org/org.el (org-doi-server-url): * lisp/textmodes/bibtex.el (bibtex-generate-url-list): Prefer https: to http: un URLs.
Diffstat (limited to 'doc/lispref/package.texi')
-rw-r--r--doc/lispref/package.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/lispref/package.texi b/doc/lispref/package.texi
index eb34b8e0af2..57f4cbc5db3 100644
--- a/doc/lispref/package.texi
+++ b/doc/lispref/package.texi
@@ -159,7 +159,7 @@ the various headers, as illustrated by the following example:
;; Version: 1.3
;; Package-Requires: ((flange "1.0"))
;; Keywords: multimedia, hypermedia
-;; URL: http://example.com/jrhacker/superfrobnicate
+;; URL: https://example.com/jrhacker/superfrobnicate
@dots{}
@@ -351,7 +351,7 @@ for a multi-file package, it is the package tar file.
You can also sign the archive's contents file in the same way.
Make the @file{.sig} files available in the same location as the packages.
You should also make your public key available for people to download;
-e.g., by uploading it to a key server such as @url{http://pgp.mit.edu/}.
+e.g., by uploading it to a key server such as @url{https://pgp.mit.edu/}.
When people install packages from your archive, they can use
your public key to verify the signatures.