Re: elpa.git and `new-master`

[Eli Zaretskii]

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: emacs-devel@gnu.org
> Date: Tue, 15 Dec 2020 16:33:14 -0500
> 
> >> Could you clarify what you mean by "maintain the Git repository"?
> > It's just the result of cloning the ELPA repository.
> 
> Cloning is a pretty small part of "maintaining" and is usually useless
> on its own.  So give an example of what you want to do.  It would start
> with
> 
>     git clone .../elpa.git
> 
> presumably, but the interesting part is what you want to do after that.

  emacs -Q
  M-: (add-to-list 'load-path ".../elpa/packages/FOO") RET
  M-x load-library FOO RET
  <use package FOO>

> >> A normal clone of the elpa.git repository will include all the packages,
> >> as before, none of them in `master` or `new-master`, tho: all of them in
> >> externals/[PKGNAME] branches.
> >> 
> >>     make packages/[PKGNAME]
> >> 
> >> will bring a specific package into its `packages/[PKGNAME]` subdirectory
> >> (by way of `git worktree`).
> >
> > So I will have to use 'make' to get every single package?
> 
> No: `make externals` works as before to populate `packages` with all the
> packages, if that's what you're after.  In that case, nothing has
> changed from before, mostly (except that if you want to commit changes
> to a particular package, you have to do so from the
> `packages/[PKGNAME]` subdirectory).

Maybe I'm confused, but my understanding was that more packages will
now need to be treated as "externals".