From: zimoun <zimon.toutoune@gmail.com>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 44555@debbugs.gnu.org, Andrew Tropin <andrew@trop.in>
Subject: [bug#44555] [PATCH] gnu: Add emacs-next-use-package
Date: Wed, 11 Nov 2020 23:42:55 +0100 [thread overview]
Message-ID: <861rgza51s.fsf@gmail.com> (raw)
In-Reply-To: <6c53dfc16470d83a8e73eeaee56dd7fed2843518.camel@student.tugraz.at>
Dear,
On Tue, 10 Nov 2020 at 19:00, Leo Prikler <leo.prikler@student.tugraz.at> wrote:
> it was me, who suggested (in IRC) to keep two different packages, as it
> appeared to me to be a non-trivial transaction (given the changes to
> propagated-inputs) with the intent to make things run on Emacs 28. I
> did try to point out, that it can/should be built with Emacs 28, but
> there appears to have been some miscommunication.
Thank you both for the explanations. Well, the fix has finally been
from upstream, if I read correctly. :-)
However, Guix is still missing a good story to build the Emacs packages
using ’emacs-minimal’ or ’emacs-next’ or any other elisp bytecode
compiler (emacs-guile, REmacs, emacs-gccjit, etc.).
All the best,
simon
prev parent reply other threads:[~2020-11-11 22:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 15:45 [bug#44555] [PATCH] gnu: Add emacs-next-use-package Andrew Tropin
2020-11-10 16:15 ` Andrew Tropin
2020-11-10 17:16 ` zimoun
2020-11-10 17:56 ` Andrew Tropin
2020-11-10 19:22 ` Michael Rohleder
2020-11-10 19:36 ` Andrew Tropin
2020-11-10 20:32 ` Michael Rohleder
2020-11-11 7:53 ` Andrew Tropin
2020-11-11 9:35 ` Nicolas Goaziou
2020-11-11 10:02 ` bug#44555: " Nicolas Goaziou
2020-11-11 14:33 ` [bug#44555] " Andrew Tropin
2020-11-10 18:00 ` Leo Prikler
2020-11-11 22:42 ` zimoun [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=861rgza51s.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=44555@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=leo.prikler@student.tugraz.at \
/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/guix.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).