emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Candidate packages for ELPA bundling [Was: Re: Why not include all E


From: Dmitry Gutov
Subject: Re: Candidate packages for ELPA bundling [Was: Re: Why not include all ELPA packages in an Emacs release?]
Date: Sat, 8 Jun 2024 05:11:15 +0300
User-agent: Mozilla Thunderbird

On 08/06/2024 04:44, Po Lu wrote:
Jeremy Bryant<jb@jeremybryant.net>  writes:

How about selecting 1 package to work on bundling by ease of
implementation.

For example, Philip's auto-header package is on ELPA, and Philip has
ELPA knowledge.  Philip, WDYT?

(Reviewing the feature branches they are constructed in terms of general
examples, it may help to have a concrete single package to work on bundling?)
And what of us sods who must build Emacs from the source code
repository?  It would be awful if features bundled in source tarballs
were to be absent from, for instance, the Android redistributables:

   https://sourceforge.net/projects/android-ports-for-gnu-emacs

and downloading dozens of ELPA repositories before each build, not to
mention repairing the inevitable incompatibility from time to time, is
not an enviable prospect in any sense.

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'.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]