File: package-vc.el.html
While packages managed by package.el use tarballs for distributing the source code, this extension allows for packages to be fetched and upgraded directly from a version control system.
To install a package from source use package-vc-install. If you
aren't interested in activating a package, you can use
package-vc-checkout instead, which will prompt you for a target
directory. If you wish to reuse an existing checkout, the command
package-vc-install-from-checkout will create a symbolic link and
prepare the package.
If you make local changes that you wish to share with an upstream
maintainer, the command package-vc-prepare-patch can prepare
these as patches to send via Email.
Defined variables (10)
package-vc--archive-data-alist | List of package specification metadata for archives. |
package-vc--archive-spec-alists | List of package specifications for each archive. |
package-vc--backend-type | The type of VC backends that support cloning package VCS repositories. |
package-vc--elpa-packages-version | Version number of the package specification format understood by package-vc. |
package-vc-allow-build-commands | Whether to run extra build commands when installing VC packages. |
package-vc-default-backend | Default VC backend to use for cloning package repositories. |
package-vc-heuristic-alist | Alist mapping repository URLs to VC backends. |
package-vc-non-code-file-names | List of file names that do not contain Emacs Lisp code. |
package-vc-register-as-project | Non-nil means that packages should be registered as projects. |
package-vc-selected-packages | List of packages to install from their VCS repositories. |