From: phillip.lord@russet.org.uk (Phillip Lord)
To: emacs-devel@gnu.org
Subject: In Support of ELPA
Date: Tue, 11 Jul 2017 22:46:36 +0100 [thread overview]
Message-ID: <87eftmejer.fsf@russet.org.uk> (raw)
Following on from the emails about magit, I am going to have a go at
getting copyright assignments for it, so that it can be included in
either ELPA or Emacs.
I've already discussed the pain points with the copyright assignment,
but an additional issue is how to get code into ELPA. With dash.el, I
added the dash repo as an "external" branch into ELPA.
I think, though, this is still a bit clunky. I think it would be nice to
add support for MELPA recipes directly in ELPA. This was adding an MELPA
package to ELPA would require simply copying the recipe from MELPA.
Assuming we support only MELPAs git (and github maybe) recipes, this
could be done by either creating a new external branch for ELPA, or
updating an existing branch from downstream. This functionality fits
directly on topic of the existing ELPA code.
Anyone have thoughts? And would any one be interested on adding it, as I
will struggle to do this as well as working on assignments.
Phil
next reply other threads:[~2017-07-11 21:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 21:46 Phillip Lord [this message]
2017-07-11 22:37 ` In Support of ELPA Stefan Monnier
2017-07-12 13:30 ` Ted Zlatanov
2017-07-13 12:23 ` Richard Stallman
2017-07-13 15:05 ` Ted Zlatanov
2017-07-13 22:02 ` Phillip Lord
2017-07-13 16:15 ` Phillip Lord
2017-07-14 1:20 ` Richard Stallman
2017-07-14 10:02 ` Phillip Lord
2017-07-16 1:50 ` Richard Stallman
2017-07-17 14:05 ` Phillip Lord
2017-07-14 2:12 ` Stefan Monnier
2017-07-14 6:48 ` Thien-Thi Nguyen
2017-07-15 1:35 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eftmejer.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).