Package.el - Revision history

Elvince: see also: Borg

2017-11-15T09:49:23Z

2017-08-15T03:21:37Z

Remove some wrong information about straight.el, and add some correct information instead

2017-07-13T13:02:32Z

about straight.el, another package manager

2017-07-12T21:46:28Z

Install packages automatically on startup: more fixes

2017-07-10T07:55:06Z

Install packages automatically on startup: cl is deprecated why do people still suggest to use it

2017-06-12T21:35:35Z

2017-05-17T17:09:49Z

Install packages automatically on startup: use-package and Cask

2017-05-17T17:06:21Z

How to use it with a custom build: change title: install packages on startup

2016-02-27T12:16:40Z

Try packages without installing them

2016-01-16T21:37:40Z

Select Packages from the List: provide detail on how to update packages.

@@ Line 155: / Line 155: @@
 * straight.el uses the init-file as a sole source of truth, whereas package.el stores mutable state outside the init-file
 * straight.el focuses on reproducibility and local modification, neither of which are supported in any way by package.el
 == External links ==

@@ Line 148: / Line 148: @@
 === Straight.el, an alternative package manager ===
-[https://github.com/raxod502/straight.el straight.el] is a "Next-generation, purely functional package manager for the Emacs hacker". It is compatible with ELPA, MELPA, Marmelade and co.
+[https://github.com/raxod502/straight.el straight.el] is a "Next-generation, purely functional package manager for the Emacs hacker".
 == External links ==

← Older revision		Revision as of 13:02, 13 July 2017
Line 145:		Line 145:

	you can also put an url pointing to a .el file.		you can also put an url pointing to a .el file.
		+
		+	=== Straight.el, an alternative package manager ===
		+
		+	[https://github.com/raxod502/straight.el straight.el] is a "Next-generation, purely functional package manager for the Emacs hacker". It is compatible with ELPA, MELPA, Marmelade and co.

	== External links ==		== External links ==

@@ Line 64: / Line 64: @@
 (defun my-packages-installed-p ()
    (cl-loop for p in my-packages
-            when (not (package-installed-p p)) do (return nil)
+            when (not (package-installed-p p)) do (cl-return nil)
-            finally (return t)))
+            finally (cl-return t)))
 (unless (my-packages-installed-p)

@@ Line 52: / Line 52: @@
 <source lang="lisp">
 ;; Comment out if you've already loaded this package...
-(require 'cl)
+(require 'cl-lib)
 (defvar my-packages
@@ Line 63: / Line 63: @@
 (defun my-packages-installed-p ()
-   (loop for p in my-packages
+   (cl-loop for p in my-packages
-        when (not (package-installed-p p)) do (return nil)
+           when (not (package-installed-p p)) do (return nil)
-        finally (return t)))
+           finally (return t)))
 (unless (my-packages-installed-p)

@@ Line 123: / Line 123: @@
 * [[Marmalade]]
 * [http://slugelisp.ahungry.com/ slugelisp], an alternative website to browse all package.el packages, search by name and quickly see their documentation, and search in their documentation. It is slower than melpa.org but a bit more complete.
 == See also ==

← Older revision		Revision as of 17:09, 17 May 2017
Line 77:		Line 77:

	This code check if all of the packages in the list are installed and if any of them are not installed if refreshes the local package database (in the case a required package for recently added to the remote repo) and installs them.		This code check if all of the packages in the list are installed and if any of them are not installed if refreshes the local package database (in the case a required package for recently added to the remote repo) and installs them.
		+
		+	=== use-package ===
		+
		+	But the [https://github.com/jwiegley/use-package use-package] macro (by J. Wingley, Emacs maintainer) also helps in doing that, and more. It allows to declare packages, install and load them asynchronously and declare their configuration.
		+
		+	=== Cask ===
		+
		+
		+	[https://cask.github.io/ Cask] is a project management tool for Emacs that helps automate the package development cycle; development, dependencies, testing, building, packaging and more.
		+
		+	Cask can also be used to manage dependencies for your local Emacs configuration.

	== How to publish it to Marmalade ==		== How to publish it to Marmalade ==

@@ Line 46: / Line 46: @@
 There's also [http://melpa.org MELPA], which is the largest and most comprehensive package repository: it builds packages directly from the source-code control systems of upstream developers, which can then conveniently be installed by end users via <tt>package.el</tt>.
-== How to use it with a custom build ==
+== Install packages automatically on startup ==
 Using the <tt>package.el</tt> UI is ok if you’re a casual Emacs user, but what if you have a custom Emacs configuration, stored under version control, that you’d like to instantly deploy on any OS/machine (like Emacs Prelude). Here in play comes <tt>package.el</tt>’s programmer interface. In [https://github.com/bbatsov/emacs-prelude Emacs Prelude] I use the following code to install a list of required packages automatically on Emacs startup (if necessary):

← Older revision		Revision as of 12:16, 27 February 2016
Line 119:		Line 119:

	with [http://melpa.org/#/auto-package-update auto-package-update], on MELPA.		with [http://melpa.org/#/auto-package-update auto-package-update], on MELPA.
		+
		+	=== Try packages without installing them ===
		+
		+	This is possible with the package [https://github.com/larstvei/Try Try] (on melpa). Packages will be stored in a temporary directory by default.
		+
		+	To try out a package you can run:
		+
		+	M-x try RET multiple-cursors RET
		+
		+	you can also put an url pointing to a .el file.

	== External links ==		== External links ==

@@ Line 33: / Line 33: @@
 A little drawback is that some packages won't load automatically at startup. Be sure to read the package description (press Enter), you may have to add a few lines to your .emacs.
-Initially <tt>package.el</tt> didn’t provide the option to update a package, but that should be fixed in recent Emacs builds. According to this [http://lists.gnu.org/archive/html/emacs-devel/2011-09/msg00371.html thread] you can even update all of the installed packages by using the “U” key in the packages list view (I guess that a small “u” would update only one package). Unfortunately my build is lacking those capabilities so I cannot comment of their usability.
+Initially <tt>package.el</tt> didn’t provide the option to update a package, but that is fixed by now. You can press “U” (<tt>package-menu-mark-upgrades</tt>) to mark all the packages that need an update. To execute all the updates press “x”.
 == How to add additional repository ==