From: Eli Zaretskii <eliz@gnu.org>
To: phillip.lord@russet.org.uk (Phillip Lord)
Cc: emacs-devel@gnu.org
Subject: Re: Adding ELPA to Emacs core
Date: Sat, 10 Mar 2018 20:59:48 +0200 [thread overview]
Message-ID: <83lgezu57f.fsf@gnu.org> (raw)
In-Reply-To: <87efks1642.fsf@russet.org.uk> (phillip.lord@russet.org.uk)
> From: phillip.lord@russet.org.uk (Phillip Lord)
> Date: Sat, 10 Mar 2018 12:13:01 +0000
>
>
> I've had a bit of a play at allowing ELPA packages to be directly
> distributed with a core emacs installation. I tried this before where
> files from ELPA were adding into the core as package.el packages. This
> version does something simpler -- the raw files are just dumping into
> the Emacs core, and then loaded like normal.
>
> It currently uses some heuristics to achieve this, but it supports
> installing the package, any tests into EMACS/test/lisp and texinfo
> files. I've added an extensibility point though -- packages could
> control their own deployment where something complicated needs to
> happen.
>
> Currently, it's make file driven (i.e. you edit the make file to add or
> update a new package), but it would probably make sense to put the data
> in a different file.
Thanks.
Is this supposed to be used while building a development version as
well? Because if so, its use of rsync might be a portability issue.
Can't we do the same using some Git magic instead?
next prev parent reply other threads:[~2018-03-10 18:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-10 12:13 Adding ELPA to Emacs core Phillip Lord
2018-03-10 18:59 ` Eli Zaretskii [this message]
2018-03-10 20:44 ` Phillip Lord
2018-03-11 3:56 ` Stefan Monnier
2018-03-11 22:03 ` Phillip Lord
2018-03-12 19:16 ` Achim Gratz
2018-03-12 21:11 ` Phillip Lord
2018-03-13 0:53 ` Stefan Monnier
2018-03-13 17:00 ` Phillip Lord
2018-03-13 21:16 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83lgezu57f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=phillip.lord@russet.org.uk \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.