From: Eduardo Ochs <eduardoochs@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How do package.el handles "duplicate packages"?
Date: Fri, 25 Nov 2022 00:58:39 -0300 [thread overview]
Message-ID: <CADs++6iceDBc6AnGVQJ36tivM2nDG1AgxY9EtjhFM+qWui+TiA@mail.gmail.com> (raw)
In-Reply-To: <jwvmt8fu486.fsf-monnier+emacs@gnu.org>
On Fri, 25 Nov 2022 at 00:05, Stefan Monnier via Users list for the
GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
>
> More seriously, I don't think it's clearly documented there, so better
> ask more precise questions.
>
> (...)
>
> 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.
Ah, I missed that!
Note that the current docstring doesn't mention that one of the entries
is for nongnu and the other one is for melpa:
https://git.savannah.gnu.org/cgit/emacs.git/tree/lisp/emacs-lisp/package.el#n1513
(defvar package-archive-contents nil
"Cache of the contents of all archives in `package-archives'.
This is an alist mapping package names (symbols) to
non-empty lists of `package-desc' structures.")
Anyway, if I change the cl-loop in my previous e-mail to this,
(setq my-ps
(cl-loop for (name . pdescs) in package-archive-contents
if (> (length pdescs) 1)
collect (cons name pdescs)))
it produces a list of the packages with duplicate entries, and I can
use that to compare the two entries.
Next question: is there a way to determine which of the entries -
nongnu or melpa - corresponds to a version that is more recent?
Thanks in advance! =)
Eduardo Ochs
http://angg.twu.net/#eev
next prev parent reply other threads:[~2022-11-25 3:58 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
2022-11-25 3:58 ` Eduardo Ochs [this message]
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=CADs++6iceDBc6AnGVQJ36tivM2nDG1AgxY9EtjhFM+qWui+TiA@mail.gmail.com \
--to=eduardoochs@gmail.com \
--cc=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).