emacs-devel
[Top][All Lists]
Advanced

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

Re: [Emacs-diffs] feature/integrated-elpa 4f6df43 15/23: README added


From: Phillip Lord
Subject: Re: [Emacs-diffs] feature/integrated-elpa 4f6df43 15/23: README added
Date: Sat, 17 Sep 2016 22:25:29 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)

Stefan Monnier <address@hidden> writes:

>> I've not had any experience with git subtree, but regardless, it's only
>> one possibility. My proof-of-principle is agnostic to how packages get
>> into the build. They could be pushed there with git subtree, checkouted
>> of ELPA (as ELPA does with externals), or just plain copied there.
>
> Good.  Extra support to do the checkout from elpa.git would be great.


I've been thinking a little bit about this -- in terms of the features
that would be needed, as opposed to implementation.

So far I have the ability to:

 - include some but not all packages from ELPA
 - use a specific commit/branch in ELPA which may not be the latest
 - access both external and, erm, non-external packages from ELPA
 - potentially fork the version in ELPA

My feeling is that, if we are going to produce a tarball build with ELPA
packages this still needs to be repeatable.

I do not know how to support packages like seq.el where the version in
ELPA and in core are just different. I guess either ELPA needs to
support multiple versions (i.e. different Emacs versions download
different things), or maybe some "with-version" macros.

If you have any ideas or features you want, let me know -- either here
or add a TODO.org file to the branch!

Phil



reply via email to

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