with the maintainers, first commit your changes then use the command
@code{package-vc-prepare-patch} to share it. @xref{Preparing Patches}.
-@findex package-vc-link-directory
+@findex package-vc-install-from-checkout
@findex package-vc-refresh
If you maintain your own packages you might want to use a local
checkout instead of cloning a remote repository. You can do this by
-using @code{package-vc-link-directory}, which creates a symbolic link
+using @code{package-vc-install-from-checkout}, which creates a symbolic link
from the package directory (@pxref{Package Files}) to your checkout
and initialises the code. Note that you might have to use
@code{package-vc-refresh} to repeat the initialisation and update the
repository.
+++
-*** New command 'package-vc-link-directory'
+*** New command 'package-vc-install-from-checkout'
An existing checkout can now be loaded via package.el, by creating a
symbolic link from the usual package directory to the checkout.
;; 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 re-use an existing checkout, the command
-;; `package-vc-link-directory' will create a symbolic link and prepare
-;; the package.
+;; `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
(find-file directory)))
;;;###autoload
-(defun package-vc-link-directory (dir name)
+(defun package-vc-install-from-checkout (dir name)
"Set up the package NAME in DIR by linking it into the ELPA directory.
Interactively, prompt the user for DIR, which should be a directory
under version control, typically one created by `package-vc-checkout'.