TakeV
/
spacemacs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
spacemacs/.lock

21 lines
675 B
Plaintext
Raw Normal View History

core: add support for stable ELPA repository hosted on GitHub Use the official spacelpa ELPA repository. address: https://github.com/syl20bnr/spacelpa ELPA repository configuration is now in a file called .lock at the root of the git repository. Its goal is to setup the ELPA repositories for a given branch and it should not be modified! The philosophy of Spacemacs is to never fork the git repository and this lock file has been put in the repo on purpose. Only the master branch will have a .lock file that points to spacelpa, the develop branch won't use the stable ELPA repository and will continue to behave like it always did. BUT for testing purpose and until the first major version of Spacemacs that uses the stable ELPA repo is released I push a .lock file to develop branch that points to spacelpa. I understand that some people can be annoyed by this so the variable configuration-layer--elpa-archives can be overriden by putting a setq in your dotfile in the user-init function like this: (setq configuration-layer--elpa-archives '(("melpa" . "melpa.org/packages/") ("org" . "orgmode.org/elpa/") ("gnu" . "elpa.gnu.org/packages/")))
2017-10-29 04:28:22 +00:00
;; -*- mode: emacs-lisp -*-
core: change scope of elpa stable variables make them public when they are used outside of core-configuration-layer.el make them private when they are used only on this file.
2017-11-02 03:13:47 +00:00
(setq configuration-layer-stable-elpa-name "spacelpa")
(setq configuration-layer-stable-elpa-version "0.300")
core: for elpa dir, replace branch name by a variable set in .lock New variable configuration-layer-elpa-subdirectory set in .lock file. Now users creating a branch based on develop or master won't reinstall all the packages in a new elpa directory.
2017-11-02 03:23:26 +00:00
(setq configuration-layer-elpa-subdirectory "develop")
core: add support for stable ELPA repository hosted on GitHub Use the official spacelpa ELPA repository. address: https://github.com/syl20bnr/spacelpa ELPA repository configuration is now in a file called .lock at the root of the git repository. Its goal is to setup the ELPA repositories for a given branch and it should not be modified! The philosophy of Spacemacs is to never fork the git repository and this lock file has been put in the repo on purpose. Only the master branch will have a .lock file that points to spacelpa, the develop branch won't use the stable ELPA repository and will continue to behave like it always did. BUT for testing purpose and until the first major version of Spacemacs that uses the stable ELPA repo is released I push a .lock file to develop branch that points to spacelpa. I understand that some people can be annoyed by this so the variable configuration-layer--elpa-archives can be overriden by putting a setq in your dotfile in the user-init function like this: (setq configuration-layer--elpa-archives '(("melpa" . "melpa.org/packages/") ("org" . "orgmode.org/elpa/") ("gnu" . "elpa.gnu.org/packages/")))
2017-10-29 04:28:22 +00:00
core: change scope of elpa stable variables make them public when they are used outside of core-configuration-layer.el make them private when they are used only on this file.
2017-11-02 03:13:47 +00:00
(setq configuration-layer-elpa-archives
core: add support for stable ELPA repository hosted on GitHub Use the official spacelpa ELPA repository. address: https://github.com/syl20bnr/spacelpa ELPA repository configuration is now in a file called .lock at the root of the git repository. Its goal is to setup the ELPA repositories for a given branch and it should not be modified! The philosophy of Spacemacs is to never fork the git repository and this lock file has been put in the repo on purpose. Only the master branch will have a .lock file that points to spacelpa, the develop branch won't use the stable ELPA repository and will continue to behave like it always did. BUT for testing purpose and until the first major version of Spacemacs that uses the stable ELPA repo is released I push a .lock file to develop branch that points to spacelpa. I understand that some people can be annoyed by this so the variable configuration-layer--elpa-archives can be overriden by putting a setq in your dotfile in the user-init function like this: (setq configuration-layer--elpa-archives '(("melpa" . "melpa.org/packages/") ("org" . "orgmode.org/elpa/") ("gnu" . "elpa.gnu.org/packages/")))
2017-10-29 04:28:22 +00:00
`(("melpa" . "melpa.org/packages/")
("org" . "orgmode.org/elpa/")
("gnu" . "elpa.gnu.org/packages/")
core: change scope of elpa stable variables make them public when they are used outside of core-configuration-layer.el make them private when they are used only on this file.
2017-11-02 03:13:47 +00:00
("spacelpa" . ,(concat configuration-layer-stable-elpa-directory
core: add support for stable ELPA repository hosted on GitHub Use the official spacelpa ELPA repository. address: https://github.com/syl20bnr/spacelpa ELPA repository configuration is now in a file called .lock at the root of the git repository. Its goal is to setup the ELPA repositories for a given branch and it should not be modified! The philosophy of Spacemacs is to never fork the git repository and this lock file has been put in the repo on purpose. Only the master branch will have a .lock file that points to spacelpa, the develop branch won't use the stable ELPA repository and will continue to behave like it always did. BUT for testing purpose and until the first major version of Spacemacs that uses the stable ELPA repo is released I push a .lock file to develop branch that points to spacelpa. I understand that some people can be annoyed by this so the variable configuration-layer--elpa-archives can be overriden by putting a setq in your dotfile in the user-init function like this: (setq configuration-layer--elpa-archives '(("melpa" . "melpa.org/packages/") ("org" . "orgmode.org/elpa/") ("gnu" . "elpa.gnu.org/packages/")))
2017-10-29 04:28:22 +00:00
"spacelpa-"
core: change scope of elpa stable variables make them public when they are used outside of core-configuration-layer.el make them private when they are used only on this file.
2017-11-02 03:13:47 +00:00
configuration-layer-stable-elpa-version))))
core: add support for stable ELPA repository hosted on GitHub Use the official spacelpa ELPA repository. address: https://github.com/syl20bnr/spacelpa ELPA repository configuration is now in a file called .lock at the root of the git repository. Its goal is to setup the ELPA repositories for a given branch and it should not be modified! The philosophy of Spacemacs is to never fork the git repository and this lock file has been put in the repo on purpose. Only the master branch will have a .lock file that points to spacelpa, the develop branch won't use the stable ELPA repository and will continue to behave like it always did. BUT for testing purpose and until the first major version of Spacemacs that uses the stable ELPA repo is released I push a .lock file to develop branch that points to spacelpa. I understand that some people can be annoyed by this so the variable configuration-layer--elpa-archives can be overriden by putting a setq in your dotfile in the user-init function like this: (setq configuration-layer--elpa-archives '(("melpa" . "melpa.org/packages/") ("org" . "orgmode.org/elpa/") ("gnu" . "elpa.gnu.org/packages/")))
2017-10-29 04:28:22 +00:00
(setq package-archive-priorities
'(("spacelpa" . 8)
("melpa" . 4)
("org" . 2)
("gnu" . 1)))