From: Liliana Marie Prikler <liliana.prikler@ist.tugraz.at>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 56376@debbugs.gnu.org, Philip McGrath <philip@philipmcgrath.com>
Subject: bug#56376: emacs-guix missing from package-activated-list
Date: Wed, 04 Oct 2023 08:13:49 +0200 [thread overview]
Message-ID: <e5d1dc9584abcee4b54267d1281ff0bad35c6803.camel@ist.tugraz.at> (raw)
In-Reply-To: <87fs2r3wt7.fsf@gmail.com>
Am Dienstag, dem 03.10.2023 um 23:12 -0400 schrieb Maxim Cournoyer:
> Hi,
>
> Liliana Marie Prikler <liliana.prikler@ist.tugraz.at> writes:
>
> > Am Sonntag, dem 03.07.2022 um 21:33 -0400 schrieb Philip McGrath:
> > > Hi,
> > >
> > > I've been looking into managing my Emacs packages with Guix. I
> > > found that the `emacs-guix` package doesn't seem to show up in
> > > the `package-activated-list`, even though its dependencies do,
> > > which seems like a bug.
> > This might be related to the fact that Emacs doesn't see guix as a
> > package. I think the recipe might be missing the -pkg.el
> > autogeneration we added to emacs-build-system.
>
> We could workaround the problem using the ensure-package-description
> of the emacs-build-system phase, but since the emacs-guix package
> uses the gnu-build-system, we'd also need to manually install the -
> pkg.el file generated by the phase.
>
> Since we maintain the package in Savannah, it seems it'd be more
> elegant to have an emacs-guix-pkg.el file templated by the GNU build
> system and installed by it.
Indeed, maintaining a proper package description upstream is the
preferable option.
Cheers
prev parent reply other threads:[~2023-10-04 6:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 1:33 bug#56376: emacs-guix missing from package-activated-list Philip McGrath
2022-07-04 6:40 ` Liliana Marie Prikler
2023-10-04 3:12 ` Maxim Cournoyer
2023-10-04 6:13 ` Liliana Marie Prikler [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=e5d1dc9584abcee4b54267d1281ff0bad35c6803.camel@ist.tugraz.at \
--to=liliana.prikler@ist.tugraz.at \
--cc=56376@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=philip@philipmcgrath.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 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).