[Top][All Lists]

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

Re: ELPA policy

From: Dmitry Gutov
Subject: Re: ELPA policy
Date: Mon, 9 Nov 2015 18:15:28 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Thunderbird/42.0

On 11/09/2015 06:05 PM, Eli Zaretskii wrote:

Nothing prevents us from making the same arrangements in the Emacs
repository as we have in ELPA, and then users could add the Emacs
repository to their list of sites that package.el knows about.

Create yet another package archive? With a separate publishing mechanism?

Besides, most core packages don't need any elaborate setup, you just
drop them in and restart Emacs.

"Just drop them in" doesn't address the issue of package updates, not in the slightest.

How will that change if we move them outside Emacs?  It's not like
there's some magic at ELPA that just putting a package there magically
resolves all these issues.  And if someone will have to work on that,
she can do that without moving the package aside.

They will be forced to declare the required Emacs version, for one. And abide by it.

But yes, that's also possible to do inside the Emacs repo.

There were different suggestions, with different degrees between "let's
move Org and Gnus out" and "let's move everything out".

I didn't see any.

All right, then. Let me make one right now: let's move out Org, Gnus and CEDET. And consider doing that with any other big codebase that's also maintained separately (Calc comes to mind).

There have been objections to doing that for each of these packages, but there you go. Suggestion made.

reply via email to

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