From: zimoun <zimon.toutoune@gmail.com>
To: guix-devel@gnu.org
Cc: Philip Kaludercic <philipk@posteo.net>
Subject: Re: Packages for old Emacs versions
Date: Tue, 08 Mar 2022 13:05:40 +0100 [thread overview]
Message-ID: <878rtk4pkb.fsf@gmail.com> (raw)
In-Reply-To: <87y21n3x99.fsf@posteo.net>
Hi Philip,
If I read correctly, the repositority [1] provides many recipes which
create various Emacs VM. Cool!
Well, from my point of view, these should live in a channel. Maybe the
channel guix-past is a good location. Somehow, it would be better to
have a channel with binary substitutes.
That's the easy part, somehow. Using one of these old Emacs VM, then
the user cannot install any Emacs package via Guix -- because the Emacs
packages provided by Guix are bytecompiled by the emacs-build-system
using the package emacs-minimal and thus although the bytecode is
"stable", there is not guarantee that it is compatible. Concretely,
guix install emacs@24 emacs-foo
then 'M-x foo' and who knows if it would work. The Emacs packages have
to be rebuild using the correct Emacs VM -- in the example Emacs 24.
From my point of view, the best is to use packages transformations.
Give a look at:
https://issues.guix.gnu.org/41732
for instance, let say 'package-with-explicit-emacs' and it would ease to
get one old Emacs VM and Emacs packages build with it. WDYT?
This 'package-with-explicit-emacs' could be provided by Guix itself;
which help for testing 'emacs-next', say.
The old Emacs VM could be in a channel, say guix-past. Then, this very
same transformation could be applied.
Cheers,
simon
1: https://git.sr.ht/~pkal/guix-emacs-historical
prev parent reply other threads:[~2022-03-08 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-06 15:40 Packages for old Emacs versions Philip Kaludercic
2022-03-08 1:20 ` Thiago Jung Bauermann
2022-03-13 20:53 ` Philip Kaludercic
2022-03-15 8:08 ` Ludovic Courtès
2022-03-16 16:08 ` Philip Kaludercic
2022-03-08 12:05 ` 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=878rtk4pkb.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=philipk@posteo.net \
/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).