diff options
| -rw-r--r-- | doc/emacs/package.texi | 19 |
1 files changed, 10 insertions, 9 deletions
diff --git a/doc/emacs/package.texi b/doc/emacs/package.texi index 584f85567f2..f5301b73067 100644 --- a/doc/emacs/package.texi +++ b/doc/emacs/package.texi | |||
| @@ -534,15 +534,16 @@ system-wide package directory, the deletion command signals an error. | |||
| 534 | 534 | ||
| 535 | @node Package from Source | 535 | @node Package from Source |
| 536 | @section Package from Source | 536 | @section Package from Source |
| 537 | @cindex package source vcs git @c "git" is not technically correct | 537 | @cindex package development source |
| 538 | @c but it is a popular term | 538 | @cindex upstream source, for packages |
| 539 | 539 | @cindex git source of package @c "git" is not technically correct | |
| 540 | By default @code{package-install} will download a Tarball from a | 540 | |
| 541 | package archive and install the files therein contained. Most of the | 541 | By default @code{package-install} downloads a Tarball from a package |
| 542 | time this is just what you want. One exception is when you decide to | 542 | archive and installs its files. This might be inadequate if you wish |
| 543 | hack on the source code of a package, and would like to share these | 543 | to hack on the package sources and share your changes with others. In |
| 544 | changes with other users. In that case you usually want to fetch and | 544 | that case, you may prefer to directly fetch and work on the upstream |
| 545 | work on the upstream source, so that you can prepare a usable patch. | 545 | source. This often makes it easier to develop patches and report |
| 546 | bugs. | ||
| 546 | 547 | ||
| 547 | @findex package-vc-install | 548 | @findex package-vc-install |
| 548 | One way to do this is to use @code{package-vc-install}, to fetch the | 549 | One way to do this is to use @code{package-vc-install}, to fetch the |