Re: Candidate packages for ELPA bundling [Was: Re: Why not include all ELPA packages in an Emacs release?]

[Philip Kaludercic]

Po Lu <luangruo@yahoo.com> writes:

> Dmitry Gutov <dmitry@gutov.dev> writes:
>
>> JFYI, only the ELPA repository should be necessary. The
>> internal/external packages only differ in how they are tracked in that
>> repository - but they are tracker anyway.
>>
>> The "external" packages are tracked in separate branches (called
>> external/<package-name>) - but you can get all of their contents with
>> 'git fetch'.
>
> OK, but that solves none of the other problems I raised.

How come?  If we were to copy the branches from elpa.git to emacs.git
and adjust the build system in such a way that the packages are checked
out using worktrees (as elpa-admin does), then the bundled packages
should be made available as a side-effect of trying to build Emacs.

-- 
        Philip Kaludercic on peregrine