From: "Feng Shu" <tumashu@163.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Some question about external method of elpa
Date: Mon, 17 Dec 2018 21:41:25 +0800 [thread overview]
Message-ID: <87d0q0w9ru.fsf@163.com> (raw)
In-Reply-To: <jwvwoo8n6rx.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Sun, 16 Dec 2018 23:06:31 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> 1. Does elpa cron auto call "make external" or similar process to
>> check out all the external packages?
>
> Pretty much, yes.
This is important info, suggest add it to README.
>
>> 2. If cron auto checkout external packages, does package author need
>> manual-checkout?
>
> I don't understand the question. When? Where?
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.
Now, I have know that when I use external my code is managed in
posframe.git, and push to remote elpa, I do not need download elpa.git,
why I need "make externals" if cron auto run it ?
#+BEGIN_COMMENT
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:
git push elpa <mybranch>:externals/<pkgname>
Then edit the `externals-list' file as mentioned above, and push that
change to `elpa's master branch.
You can check out all the external packages into the `packages' directory
with the command:
make externals
You can check out a specific external PACKAGE into the `packages'
directory with these commands:
#+END_COMMENT
>
>> 3. Does subtree method have any advanced than external branch?
>
> It's different, not really better. It's most appropriate when you
> intend to move the "upstream" from elsewhere to elpa.git.
This info is very important, suggest add to README
When I first import posframe to elpa.git, I do not know
what different between subtree and externals, I choice
subtree for the below line:
If know you don't want a local package, but don't know which of these
two options you prefer, then use a subtree.
I think many package author choice subtree instead of externals
for this info :-)
>
>> if no, what about obsolote this method? In my opinion, subtree
>> seem to very hard to manage.
>
> If you keep developing your package elsewhere, a "subtree" is indeed
> more work than an "external".
>
>> 4. I use subtree to manage posframe package, but I want to switch
>> to external branch method, how to work?
>
> 1- Create the new externals/posframe branch on elpa.git
> 2- Then "git rm package/posframe" and change the ":subtree" to
> a ":external" in "externals-list".
> 3- Then push those changes you created at step (2) to the `master` branch
> of elpa.git.
>
> That's pretty much it on your side (I'll probably have to do some clean
> on elpa.gnu.org in response to that, tho I keep hoping that I finally
> fixed the last issue in the scripts to handle this situation).
>
>> what about create a subtree2external command?
>
> The demand hasn't been very high, so I wouldn't bother, but fee free to
> add one to elpa.git's "admin/" subdirectory.
>
>
> Stefan
--
next prev parent reply other threads:[~2018-12-17 13:41 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 [this message]
2018-12-17 14:06 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d0q0w9ru.fsf@163.com \
--to=tumashu@163.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).