Re:Re: Some question about external method of elpa

[tumashu <tumashu@163.com>]

At 2018-12-18 03:03:40, "Stefan Monnier" <monnier@IRO.UMontreal.CA> wrote:
>>> If you explain/show me which part of README made you think `make
>>> externals` was needed, I can try and correct it, yes.
>> I suggest to move the below part to: To install all the packages "in
>> place".
>
>I'd rather keep it in the "externals" section, since that's what
>it's about.
>
>How 'bout the patch below instead?



>
>
>        Stefan
>
>
>diff --git a/README b/README
>index 8c85210de..bc52eb44b 100644
>--- a/README
>+++ b/README
>@@ -229,12 +229,14 @@ In the `external' case, the copy of the code is not kept in `master` but in the
> 
> To add a new externals package, first add this `elpa.git' repository as a
> new remote in your existing repository.  Then push a local branch to a
>-new remote branch in `elpa.git', named externals/<pkgname>.  For example:
>+new remote branch in `elpa.git', named `externals/<pkgname>`.  For example:
> 
>    git push elpa <mybranch>:externals/<pkgname>
> 
> Then edit the `externals-list' file as mentioned above, and push that
>-change to `elpa's master branch.
>+change to `elpa's master branch.  After it's added to the `externals-list'
>+file, the package can be maintained just by pushing changes to the
>+`externals/<pkgname>` branch.

Seem to ok :-)

> 
> You can check out all the external packages into the `packages' directory
> with the command:

What about change this line to: 

If you wish to check out all the external packages into the `packages' dirctory
for personal reason, you can run the command: