From: "Ludovic Courtès" <ludo@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 38643-done@debbugs.gnu.org, saffronsnail <saffronsnail@protonmail.com>
Subject: bug#38643: [PATCH] Add spacemacs package
Date: Tue, 12 Apr 2022 20:12:51 +0200 [thread overview]
Message-ID: <87o816cgrg.fsf@gnu.org> (raw)
In-Reply-To: <867d7u37xg.fsf_-_@gmail.com> (zimoun's message of "Tue, 12 Apr 2022 12:36:11 +0200")
Hi,
zimoun <zimon.toutoune@gmail.com> skribis:
> What is the next action? Is it worth to include it despite the fact
> that:
>
> > Do I get it right that Spacemacs will try to fetch the
> > packages it needs via pkg.el (ELPA)?
> >
> > Longer-term, it would be nice if it could fetch packages
> > through Guix, using Emacs-Guix. Are you familiar with this
> > part of Spacemacs?
>
> I agree that this should be the long-term plan, though I would
> like to avoid the overhead of maintaining each individual ELPA
> package separately. I have not `guix import`ed an ELPA package
> before, but I know that for some other imports manual fixup is
> needed. Do you know if this is the case for ELPA? If so, I would
> prefer to work on a way to fix that than to manually maintain
> dozens of packages.
>
> or do we drop it?
Given that it hasn’t seen any activity, I believe we can close it for
now. I’d love to see proper Spacemacs integration, but for that we need
saffronsnail or another Spacemacs-savvy person to champion it.
Thanks,
Ludo’.
prev parent reply other threads:[~2022-04-12 18:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 23:05 [bug#38643] [PATCH] Add spacemacs package saffronsnail via Guix-patches via
2019-12-17 15:21 ` Ludovic Courtès
[not found] ` <X7kuwz6we7bMgo9FoBKkSRozGy8kO1DQPbYLA2OvWJ2_G2a_yS11G2Oq3cjhwmxLHg4RLC4ugs599vI_oYNnOluorFJ0V_nC6xJcPoufNr4=@protonmail.com>
2022-04-12 10:36 ` zimoun
2022-04-12 18:12 ` Ludovic Courtès [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o816cgrg.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=38643-done@debbugs.gnu.org \
--cc=saffronsnail@protonmail.com \
--cc=zimon.toutoune@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/guix.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.