unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bruce.connor.am@gmail.com, joakim@verona.se, emacs-devel@gnu.org
Subject: Re: subr-x on Elpa
Date: Wed, 20 May 2015 16:46:49 -0400	[thread overview]
Message-ID: <jwva8wzf0jt.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83382r6p0r.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 20 May 2015 22:13:24 +0300")

>> It sounds very simple, but can obviously not be simple otherwise
>> someone would have done it already.
> Mundane maintenance tasks tend to be ignored, except by a select few.

There's nothing fundamentally hard about it, tho it depends how far you
want to go.  There are several levels of "bundling", e.g.:
1- just change the make-tarball script so it includes specific GNU
   ELPA packages.   This should be easy since it only affects those rare
   release managers who build the tarball.
2- do the same plus make it so that these GNU ELPA packages are also
   included for people who install from the emacs.git checkout rather
   than from the tarball.  This should be pretty easy, but may/will
   affect everyone who checks out the emacs.git repository without the
   elpa.git, or without placing the elpa.git right where the new scripts
   want it to be.  So you can expect some complaints/resistance.
3- same as 2 plus make sure that Emacs's own packages can depend on some
   of the bundled GNU ELPA packages.

Step 3 is needed if we want to bundle seq.el, which is an obvious
candidate.

I could even imagine a step 4 where we can have some GNU ELPA packages
preloaded in the dumped `emacs'.  Tho I can't see this being used in the
foreseeable future.


        Stefan



  reply	other threads:[~2015-05-20 20:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-20 12:32 subr-x on Elpa Artur Malabarba
2015-05-20 14:07 ` Stefan Monnier
2015-05-20 14:33   ` Artur Malabarba
2015-05-20 15:35     ` Bozhidar Batsov
2015-05-20 19:04       ` Artur Malabarba
2015-05-20 18:51     ` Stefan Monnier
2015-05-20 19:02       ` joakim
2015-05-20 19:13         ` Eli Zaretskii
2015-05-20 20:46           ` Stefan Monnier [this message]
2015-05-21 10:28       ` Dmitry Gutov

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=jwva8wzf0jt.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=bruce.connor.am@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=joakim@verona.se \
    /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).