From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: "Feng Shu" <tumashu@163.com>
Cc: emacs-devel@gnu.org
Subject: Re: Some question about external method of elpa
Date: Mon, 17 Dec 2018 09:06:11 -0500 [thread overview]
Message-ID: <jwvh8fcl0fb.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87d0q0w9ru.fsf@163.com> (Feng Shu's message of "Mon, 17 Dec 2018 21:41:25 +0800")
> When I read the below part of README, I think that manual run "make externals"
> is needed :-(, so I think externals is same complicated as subtree.
`make externals` is needed if you want to have a local checkout of all
the packages is elpa.git. But if you don't care about the other
packages you don't need it.
> posframe.git, and push to remote elpa, I do not need download elpa.git,
You do need to have some part of elpa.git. For "subtree", that part is the
`master` branch, and for "external" that part is the
`external/<pkgname>` branch. And when adding the external branch you
also need the `master` branch, just to modify the `externals-list` file.
> why I need "make externals" if cron auto run it ?
You don't *need* it. You may want to use it (e.g. I use it because
I just want to have all GNU ELPA packages automatically installed, so
I build&install them in-place with `make externals; make`).
> If know you don't want a local package, but don't know which of these
> two options you prefer, then use a subtree.
Note that this phrase now says:
If you don't know which of these two options you prefer, then use an
"external" (and also if your package is large).
-- Stefan
next prev parent reply other threads:[~2018-12-17 14:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 0:49 Some question about external method of elpa Feng Shu
2018-12-17 4:06 ` Stefan Monnier
2018-12-17 13:41 ` Feng Shu
2018-12-17 14:06 ` Stefan Monnier [this message]
2018-12-17 14:23 ` Feng Shu
2018-12-17 14:35 ` Stefan Monnier
2018-12-17 14:54 ` Feng Shu
2018-12-17 19:03 ` Stefan Monnier
2018-12-18 15:15 ` tumashu
2018-12-18 19:02 ` Stefan Monnier
2018-12-20 9:10 ` tumashu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvh8fcl0fb.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=tumashu@163.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.