unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Phillip Lord <phillip.lord@russet.org.uk>
To: Stephen Leake <stephen_leake@stephe-leake.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: policy discussion on bundling ELPA packages in the emacs tarball - take 2
Date: Fri, 29 Jan 2021 23:01:31 +0000	[thread overview]
Message-ID: <874kizz6t0.fsf@russet.org.uk> (raw)
In-Reply-To: <86tuqz35f1.fsf@stephe-leake.org> (Stephen Leake's message of "Fri, 29 Jan 2021 11:32:34 -0800")

Stephen Leake <stephen_leake@stephe-leake.org> writes:

> Attached is an updated version of emacs/admin/notes/elpa, describing a
> proposal for bundling ELPA packages in the emacs distribution.
>
> I believe I have included all the recent discussions.
>
> I think I figured out a way to resolve the submodles vs worktrees
> dilemma; each emacs developer can choose. If they don't execute any
> submodule commands, they can use worktrees.

That will be a significant help, actually. I presume that any build
would be missing bundled packages? For me, this would not be a hassle
because I'll just set it up so they install from ELPA on first use.

It would still break my windows packaging scripts which use worktrees,
(or as it stands the windows distribution will miss ada-mode) but I
guess that only affects me. We are some way of Emacs-28, though, so now
is a good time to break things. I would hope that big packages (org!!!)
is not going to move for a while.

Also, some research suggests that the git developers are slowing
working out how to fix the module/worktree breakage, so who knows they
might have fixed it by then.


> If we can reach consensus on this, the next step would be to create a
> feature branch and edit the code to implement this, then do a practice
> release with that branch.

It's fine with me!

Phil



  reply	other threads:[~2021-01-29 23:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29 19:32 policy discussion on bundling ELPA packages in the emacs tarball - take 2 Stephen Leake
2021-01-29 23:01 ` Phillip Lord [this message]
2021-01-30  0:07   ` Stephen Leake
2021-01-30 10:08     ` Phillip Lord
2021-01-30 10:40 ` Eli Zaretskii
2021-01-30 19:25   ` Stephen Leake

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=874kizz6t0.fsf@russet.org.uk \
    --to=phillip.lord@russet.org.uk \
    --cc=emacs-devel@gnu.org \
    --cc=stephen_leake@stephe-leake.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).