From: Stephen Leake <stephen_leake@stephe-leake.org>
To: Phillip Lord <phillip.lord@russet.org.uk>
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 16:07:16 -0800 [thread overview]
Message-ID: <86pn1n2sp7.fsf@stephe-leake.org> (raw)
In-Reply-To: <874kizz6t0.fsf@russet.org.uk> (Phillip Lord's message of "Fri, 29 Jan 2021 23:01:31 +0000")
Phillip Lord <phillip.lord@russet.org.uk> writes:
> 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?
I don't follow.
If you mean "a build from an emacs directory tree", then it will have
whatever the developer checked out into that tree.
If they did "git clone <emacs> --recurse-submodules", then the build
will have the bundled packages.
If they left --recurse-submodules off the clone, but later did either:
git submodule update --reference . --init
or:
./checkout_git_elpa_worktrees.sh
then the build will have the bundled packages.
The last option is indented for your Windows packaging workflow; it uses
git worktrees instead of submodules.
If they do neither of these options, the build will not have the 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.
This is with your emacs user hat on, I guess. Yes, using a build from an
emacs directory tree without bundled packages would require getting
those packages via M-x list-packages (or equivalent).
> It would still break my windows packaging scripts which use worktrees,
It should not, as described above.
--
-- Stephe
next prev parent reply other threads:[~2021-01-30 0:07 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
2021-01-30 0:07 ` Stephen Leake [this message]
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=86pn1n2sp7.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.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 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).