From: Andrew Tropin <andrew@trop.in>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 48331@debbugs.gnu.org, Maxim Cournoyer <maxim.cournoyer@gmail.com>
Subject: bug#48331: Emacs' describe-package doesn't work for packages managed by guix
Date: Thu, 20 May 2021 13:01:48 +0300 [thread overview]
Message-ID: <CABrWRW1DiStRz7_OTwixUH9sqcOvjJcx8Big1hmepmQWTMgdSg@mail.gmail.com> (raw)
In-Reply-To: <88a438a74fabe0f4d4bfd8a649c38e960ef82ed2.camel@student.tugraz.at>
> That looks like it'd mess with people's installed ELPA packages. In
> general, hacks based on package-directory-list don't feel very stable.
If you talk about ~/.emacs.d/elpa, it won't, because there is a separate
package-user-dir variable for that.
The problem can arise if we have emacs installed in a few profiles, I'm
not sure if it is a good idea to do so, but it is possible, in such a case
we will have a few items in the package-directory-list. A fix for that:
(setq package-directory-list
(mapcar (apply-partially 'string-remove-suffix "/elpa")
package-directory-list)))
> Also, this seems to rely on us not deleting the -pkg.el, but probably
> won't work for packages, that don't ship it, e.g. emacs-howm.
It's true, but it seems relatively easy to implement a build phase,
which will generate -pgk.el in case it is missing.
next prev parent reply other threads:[~2021-05-20 11:03 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 7:51 bug#48331: Emacs' describe-package doesn't work for packages managed by guix Andrew Tropin
2021-05-11 10:05 ` Leo Prikler
2021-05-11 15:57 ` Andrew Tropin
2021-05-11 16:33 ` Leo Prikler
2021-05-11 18:55 ` Andrew Tropin
2021-05-11 19:57 ` Leo Prikler
2021-05-19 14:32 ` Andrew Tropin
2021-05-19 15:08 ` Leo Prikler
2021-05-19 17:58 ` Andrew Tropin
2021-05-19 18:42 ` Leo Prikler
2021-05-20 10:01 ` Andrew Tropin [this message]
2021-05-20 10:20 ` Leo Prikler
2021-05-20 10:32 ` Arun Isaac
2021-05-20 10:39 ` Arun Isaac
2021-05-20 11:13 ` Leo Prikler
2021-05-20 12:24 ` Andrew Tropin
2021-05-20 15:57 ` Leo Prikler
2021-05-22 3:09 ` Maxim Cournoyer
2021-12-03 20:46 ` Liliana Marie Prikler
2021-12-06 4:52 ` Andrew Tropin
2021-12-30 8:12 ` Andrew Tropin
2021-05-11 21:17 ` Ludovic Courtès
2021-05-19 14:41 ` Andrew Tropin
2021-05-22 12:54 ` bug#48331: [PATCH 1/2] build-system: emacs: Keep -pkg.el files Leo Prikler
2021-05-22 12:54 ` bug#48331: [PATCH 2/2] gnu: emacs: Load package descriptors from packages referenced by subdirs.el Leo Prikler
2021-05-25 13:40 ` bug#48331: [PATCH draft] build-system: emacs: Generate -pkg.el file in case it is missing Andrew Tropin
2021-05-25 15:07 ` Leo Prikler
2021-05-26 8:15 ` bug#48331: [PATCH] guix: build: emacs-build-system: Make package.el aware of guix packages Ivan Sokolov
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=CABrWRW1DiStRz7_OTwixUH9sqcOvjJcx8Big1hmepmQWTMgdSg@mail.gmail.com \
--to=andrew@trop.in \
--cc=48331@debbugs.gnu.org \
--cc=leo.prikler@student.tugraz.at \
--cc=maxim.cournoyer@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.