From: Philip Kaludercic <philipk@posteo.net>
To: Po Lu <luangruo@yahoo.com>
Cc: Dmitry Gutov <dmitry@gutov.dev>,
Jeremy Bryant <jb@jeremybryant.net>,
Stefan Kangas <stefankangas@gmail.com>,
Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org, monnier@iro.umontreal.ca
Subject: Re: Candidate packages for ELPA bundling [Was: Re: Why not include all ELPA packages in an Emacs release?]
Date: Sat, 08 Jun 2024 06:41:02 +0000 [thread overview]
Message-ID: <87ikyk9bsx.fsf@posteo.net> (raw)
In-Reply-To: <87bk4cf8xr.fsf@yahoo.com> (Po Lu's message of "Sat, 08 Jun 2024 10:46:24 +0800")
Po Lu <luangruo@yahoo.com> writes:
> Dmitry Gutov <dmitry@gutov.dev> writes:
>
>> JFYI, only the ELPA repository should be necessary. The
>> internal/external packages only differ in how they are tracked in that
>> repository - but they are tracker anyway.
>>
>> The "external" packages are tracked in separate branches (called
>> external/<package-name>) - but you can get all of their contents with
>> 'git fetch'.
>
> OK, but that solves none of the other problems I raised.
How come? If we were to copy the branches from elpa.git to emacs.git
and adjust the build system in such a way that the packages are checked
out using worktrees (as elpa-admin does), then the bundled packages
should be made available as a side-effect of trying to build Emacs.
--
Philip Kaludercic on peregrine
next prev parent reply other threads:[~2024-06-08 6:41 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 8:48 Why not include all ELPA packages in an Emacs release? Jeremy Bryant
2024-05-28 23:15 ` Stefan Kangas
2024-05-28 23:56 ` Stefan Monnier
2024-05-29 5:59 ` Philip Kaludercic
2024-05-29 11:44 ` Eli Zaretskii
2024-05-29 15:27 ` Arash Esbati
2024-05-29 15:40 ` Eli Zaretskii
2024-05-29 16:06 ` Philip Kaludercic
2024-05-29 19:33 ` Andrea Corallo
2024-05-30 19:25 ` Adding AUCTeX to core " Jeremy Bryant
2024-05-30 19:33 ` Philip Kaludercic
2024-05-31 18:58 ` Jeremy Bryant
2024-06-07 22:00 ` Jeremy Bryant
2024-06-08 6:56 ` Philip Kaludercic
2024-06-08 9:40 ` Arash Esbati
2024-06-08 15:25 ` Stefan Monnier
2024-06-08 15:49 ` Po Lu
2024-06-09 3:54 ` Stefan Monnier
2024-06-09 19:39 ` Stefan Kangas
2024-05-29 22:16 ` Arash Esbati
2024-05-29 22:19 ` Dmitry Gutov
2024-05-30 6:25 ` Philip Kaludercic
2024-05-30 6:33 ` Daniel Mendler via Emacs development discussions.
2024-05-30 7:28 ` Philip Kaludercic
2024-05-30 8:15 ` Daniel Mendler via Emacs development discussions.
2024-05-30 15:20 ` Philip Kaludercic
2024-05-29 20:35 ` Tassilo Horn
2024-05-29 22:04 ` Arash Esbati
2024-05-30 5:51 ` Eli Zaretskii
2024-05-30 10:52 ` Arash Esbati
2024-05-30 5:49 ` Eli Zaretskii
2024-05-30 7:55 ` Po Lu
2024-05-30 11:20 ` Eli Zaretskii
2024-05-30 11:53 ` Po Lu
2024-05-30 12:19 ` Eli Zaretskii
2024-05-30 12:58 ` Po Lu
2024-05-30 14:11 ` Stefan Monnier
2024-05-30 14:26 ` Po Lu
2024-05-30 13:53 ` Stefan Monnier
2024-05-30 14:05 ` Po Lu
2024-05-30 15:02 ` Stefan Monnier
2024-05-30 8:00 ` Philip Kaludercic
2024-05-29 20:44 ` Stefan Kangas
2024-05-30 5:09 ` Eli Zaretskii
2024-06-07 21:48 ` Moving core packages to ELPA [Was: Re: Why not include all ELPA packages in an Emacs release?] Jeremy Bryant
2024-06-08 6:14 ` Eli Zaretskii
2024-06-08 8:10 ` Michael Albinus
2024-06-08 8:38 ` Eli Zaretskii
2024-06-08 15:55 ` Michael Albinus
2024-06-08 16:47 ` Eli Zaretskii
2024-06-08 16:59 ` Michael Albinus
2024-06-07 21:55 ` Candidate packages for ELPA bundling " Jeremy Bryant
2024-06-08 1:44 ` Po Lu
2024-06-08 2:11 ` Dmitry Gutov
2024-06-08 2:46 ` Po Lu
2024-06-08 6:41 ` Philip Kaludercic [this message]
2024-06-08 6:54 ` Po Lu
2024-06-08 7:47 ` Philip Kaludercic
2024-06-08 15:06 ` Stefan Monnier
2024-06-08 16:24 ` Philip Kaludercic
2024-06-08 15:09 ` Stefan Monnier
2024-06-08 6:25 ` Eli Zaretskii
2024-06-08 6:48 ` Po Lu
2024-06-08 15:18 ` Stefan Monnier
2024-06-08 15:37 ` Po Lu
2024-06-08 15:53 ` Stefan Monnier
2024-06-09 0:06 ` Po Lu
2024-06-09 3:55 ` Stefan Monnier
2024-06-08 6:55 ` Philip Kaludercic
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=87ikyk9bsx.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=dmitry@gutov.dev \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jb@jeremybryant.net \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@gmail.com \
/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.