[Top][All Lists]

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

Re: policy discussion on bundling ELPA packages in the emacs tarball

From: Stephen Leake
Subject: Re: policy discussion on bundling ELPA packages in the emacs tarball
Date: Mon, 25 Jan 2021 11:14:56 -0800
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (windows-nt)

Phillip Lord <phillip.lord@russet.org.uk> writes:

> Stephen Leake <stephen_leake@stephe-leake.org> writes:
>> But "copy" implies that the git information is lost, so you can't edit
>> the copy and push the changes. That won't do.
> Yes, that's the flaw, and it's a fairly big one. If you wanted to edit,
> and commit that would require checking out from the ELPA repo, updating
> the pointer on the Emacs tree and then checking back in again. 

> I solve this problem for my own packages by not installing them from
> ELPA, but from their git repos. This means normal users and me as
> developer have a different set up.

Yes; package developers edit package code in an ELPA checkout; typically
they will also run the code from there as well for testing, by putting
that directory in load-path.

But with bundled packages as submodules, they could switch to editing
them in the emacs workspace instead.

The main point is that other emacs developers can also edit the package
files, to fix bugs or make changes consistent with some core emacs change.

> straight.el solves this problem in a more principled way; the package is
> the git repo, but then the package manager is completely dependent on
> git.

>From https://github.com/raxod502/straight.el. That sounds useful.

-- Stephe

reply via email to

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