Install core packages from melpa-stable

Use-package broke in a recent update, as with Doom, since it relies so
heavily on it. To combat this issue arising again, use-package will be
installed from melpa-stable from now on.

Addresses #283
This commit is contained in:
Henrik Lissner 2017-12-04 13:22:17 -05:00
parent f617995bbe
commit 0118535267
No known key found for this signature in database
GPG key ID: 5F6C0EA160557395
2 changed files with 11 additions and 3 deletions

View file

@ -68,7 +68,7 @@ package's name as a symbol, and whose CDR is the plist supplied to its
`package!' declaration. Set by `doom-initialize-packages'.")
(defvar doom-core-packages
'(persistent-soft quelpa use-package async)
'(persistent-soft use-package quelpa)
"A list of packages that must be installed (and will be auto-installed if
missing) and shouldn't be deleted.")
@ -97,10 +97,17 @@ base by `doom!' and for calculating how many packages exist.")
package-enable-at-startup nil
package-archives
'(("gnu" . "https://elpa.gnu.org/packages/")
("melpa" . "https://melpa.org/packages/"))
("melpa" . "https://melpa.org/packages/")
("melpa-stable" . "https://stable.melpa.org/packages/"))
;; I omit Marmalade because its packages are manually submitted rather
;; than pulled, so packages are often out of date with upstream.
;; Don't gamble with these packages. Only retrieve stable versions. Quelpa
;; is omitted because it isn't on melpa-stable.
package-pinned-packages
'((use-package . "melpa-stable")
(persistent-soft . "melpa-stable"))
;; security settings
gnutls-verify-error (not (getenv "INSECURE")) ; you shouldn't use this
tls-checktrust gnutls-verify-error

View file

@ -4,6 +4,7 @@
;; core packages
(package! s)
(package! f)
(package! async)
;; core-os.el
;; In case this config is shared across multiple computers (like mine is), let's