From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: How do package.el handles "duplicate packages"?
Date: Thu, 24 Nov 2022 22:04:24 -0500 [thread overview]
Message-ID: <jwvmt8fu486.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: CADs++6gHJEvtfc60PHOCwcjr-L0xWaiYyb7vi8PcnEJpQq+KLw@mail.gmail.com
Eduardo Ochs [2022-11-24 20:43:00] wrote:
> where can I find information on how package.el handles packages that
> are listed twice in the buffer that `M-x list-packages' creates?
Hmm... in `package.el`?
More seriously, I don't think it's clearly documented there, so better
ask more precise questions.
> and I run `M-x my-p1' on the line with the first "afternoon-theme" and
> `M-x my-p2' on the second, then I can inspect the variables my-p1 and
> my-p2 with:
>
> (describe-variable 'my-p1)
> (describe-variable 'my-p2)
>
> One of them has these entries,
>
> :version (0 1)
> :archive "nongnu"
>
> and the other has these:
>
> :version (20140104 1859)
> :archive "melpa"
>
> and if I run this,
>
> (setq my-ps
> (cl-loop for (name pdesc) in package-archive-contents
> if (eq name 'afternoon-theme)
> collect (list name pdesc)))
>
> (describe-variable 'my-ps)
>
> I see only one entry in package-archive-contents - the one in MELPA...
As the docstring of `package-archive-contents` describes, there should
be only one entry for `afternoon-theme` but that entry should contain
two `package-desc` objects: one for Melpa and one for NonGNU.
Stefan
next prev parent reply other threads:[~2022-11-25 3:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 23:43 How do package.el handles "duplicate packages"? Eduardo Ochs
2022-11-25 3:04 ` Stefan Monnier via Users list for the GNU Emacs text editor [this message]
2022-11-25 3:58 ` Eduardo Ochs
2022-11-25 6:13 ` Stefan Monnier
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvmt8fu486.fsf-monnier+emacs@gnu.org \
--to=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
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).