all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: distributing Emacs modules as ELPA packages
Date: Thu, 07 Jul 2016 15:57:28 -0400	[thread overview]
Message-ID: <87twg1b4rb.fsf@lifelogs.com> (raw)
In-Reply-To: 83lh1djl25.fsf@gnu.org

On Thu, 07 Jul 2016 22:38:10 +0300 Eli Zaretskii <eliz@gnu.org> wrote: 

>> From: Ted Zlatanov <tzz@lifelogs.com>
>> Date: Thu, 07 Jul 2016 13:51:05 -0400
>> 
>> 1. We have modules in 25.1.
>> 
>> 2. 25.1 is in feature freeze (so code bindings are stable).
>> 
>> 3. We discussed putting the crypto patch in an ELPA module package years
>> ago; in fact Stefan made it a requirement:

EZ> My problem is that anyone who'd want to use that package will have to
EZ> build Emacs themselves, probably from the Git checkout.  That's not
EZ> for the faint at heart.

The package will include some metadata to tell package.el that it
requires modules enabled. Then package.el can warn appropriately when
the package or things that depend on it are requested. This metadata is
not defined currently, AFAIK.

package.el also needs logic to rebuild the module from source or install
from binaries.

None of these tasks have been done before AFAIK (which is why I asked in
the first place). Someone has to be first I guess :)

I'll work on it in a scratch branch and publish it for review when it's
ready.

Ted




      reply	other threads:[~2016-07-07 19:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07 16:27 distributing Emacs modules as ELPA packages Ted Zlatanov
2016-07-07 16:57 ` Eli Zaretskii
2016-07-07 17:08   ` Ted Zlatanov
2016-07-07 17:21     ` Eli Zaretskii
2016-07-07 17:51       ` Ted Zlatanov
2016-07-07 19:38         ` Eli Zaretskii
2016-07-07 19:57           ` Ted Zlatanov [this message]

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=87twg1b4rb.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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 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.