[Top][All Lists]

[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 08:41:20 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)

Stefan Monnier <address@hidden> writes:

>> + - Some packages are both in ELPA and core.  Currently these are
>> +   largely merged into core.  With this directory structure, we should
>> +   be able to git subtree these into here from ELPA.
> FWIW, "git subtree" is good for what it does, but having to use it sucks.
> If at all possible, we should have one and only one place where we host
> the code, so we don't need "git subtree".
> For those packages that are both "in core" and "in emacs", it'd be
> better to extract the relevant packages directly from the elpa
> repository, or vice versa (the vice versa is already supported,
> obviously).

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.

I thought git subtree might be convienient where the core package is a
slight fork of the ELPA one (as org-mode is). It may also be that we
need several solutions, depending on the package. This is one reason
that I put space for multiple subdirectories.


reply via email to

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