From: Philip Kaludercic <philipk@posteo.net>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: The place for the "ELPA bundling" project
Date: Tue, 19 Dec 2023 06:45:34 +0000 [thread overview]
Message-ID: <87frzyk7w1.fsf@posteo.net> (raw)
In-Reply-To: <4df338f6-079e-c345-718d-7ac60741bf41@gutov.dev> (Dmitry Gutov's message of "Mon, 18 Dec 2023 21:12:13 +0200")
Dmitry Gutov <dmitry@gutov.dev> writes:
> I've tried to find the bug number, or a specific emacs-devel
> discussion, that would contain the existing knowledge and some hint of
> the current state. And failed.
>
> Could somebody give me the link I could post in public? Both to refer
> to that potential feature, and to invite people to help out.
Eli send me this <83zg27emh8.fsf@gnu.org>, or if you cannot resolve it,
here is the copied text:
--8<---------------cut here---------------start------------->8---
> From: Philip Kaludercic <philipk@posteo.net>
> Cc: rms@gnu.org, emacs-devel@gnu.org
> Date: Thu, 31 Aug 2023 06:10:17 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > It is indeed planned to do that only with packages on GNU ELPA. But
> > we haven't yet figured some important aspects of including ELPA
> > packages in release tarballs, so the idea is there, but it is not yet
> > actionable.
>
> I was under the assumption that issue was resolved, if
> `package-directory-list' would contain the right directory?
That's not the only issue we need to resolve. See
https://lists.gnu.org/archive/html/emacs-devel/2020-12/msg00917.html
https://lists.gnu.org/archive/html/emacs-devel/2021-01/msg01017.html
https://lists.gnu.org/archive/html/emacs-devel/2021-01/msg01373.html
for the previous discussions, where the issues were raised and
discussed.
--8<---------------cut here---------------end--------------->8---
next prev parent reply other threads:[~2023-12-19 6:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 19:12 The place for the "ELPA bundling" project Dmitry Gutov
2023-12-19 6:45 ` Philip Kaludercic [this message]
2023-12-20 0:06 ` 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=87frzyk7w1.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=dmitry@gutov.dev \
--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 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).