From: Steve Youngs <steve@sxemacs.org>
Cc: Gnus List <ding@gnus.org>
Subject: Re: where does package-get-info get its info from?
Date: Tue, 31 Jan 2006 11:11:13 +1000 [thread overview]
Message-ID: <microsoft-free.87u0bl42xa.fsf@youngs.au.com> (raw)
In-Reply-To: <200601302339.k0UNdPND019441@athyra.sfbay.sun.com> (Mike Kupfer's message of "Mon, 30 Jan 2006 15:39:25 -0800")
[-- Attachment #1: Type: text/plain, Size: 2876 bytes --]
* Mike Kupfer <kupfer@athyra.sfbay.sun.com> writes:
SY> (package-get-info 'gnus 'date)
SY> => 2005-11-15
> Hmm. When I do that, I get
> (package-get-info 'gnus 'date)
> "2003-10-13"
> (package-get-info 'gnus 'author-version)
> "5.10.2"
...because you have _that_ version installed. :-)
> I thought it might be getting that from
> $HOME/.xemacs/package-index.LATEST.gpg
That's exactly where the info originates from. Well, some of the info
does. Some of it comes from autoloaded forms in `_pkg.el' files in
each package lisp directory.
> But if I blow away that file and invoke package-get-info in a new
> XEmacs process, it creates a new package-index.LATEST.gpg and
> gives me the same results.
Because the package-index file it created was the same as the one you
blew away. It'd just be a copy of the file that is in
/usr/local/lib/xemacs-x.x.x/etc/. And...
> The packages that I'm actually running are from a sumo that I
> unpacked in /usr/local/lib/xemacs/xemacs-packages.
...because you are a "Sumo-installer" and not a "PUI-installer", your
package-index file never gets updated. Yes, I know that seems like a
bug or flaw in the way XEmacs handles package management. But really
it isn't.
Sumo's are _not_ part of and have no knowledge of package management.
Installing a Sumo would be like getting a RPM package, converting it to
a .tar.gz and installing it with `tar zxf file.tar.gz'. The package
would install and work fine, but the underlying RPM database would have
no knowledge of it.
So, the moral to this story is: If you want the XEmacs PUI tools to
give you the best results, always install/remove/update your packages
with PUI. Sure, use the Sumo's to set up a virgin installation, but
once the Sumo is installed, continue maintaining the packages with PUI
From that point on.
I use the following incantation to keep all of my packages up to
date...
Tools -> Packages -> Set Download Site ...
Tools -> Packages -> Update Installed Packages
This elisp should also work (untested)...
,----
| (defun sy-update-my-pkgs ()
| "Just an easy way to update installed packages."
| (interactive)
| (let ((package-get-remote '("ftp.xemacs.org" "pub/xemacs/packages")))
| (package-get-update-all)))
`----
And while I'm on a roll with the recipes, this will make
`package-get-info' use a package-index from a remote package
mirror...
,----
| (let ((package-get-remote '("ftp.xemacs.org" "pub/xemacs/packages")))
| (package-get-info 'gnus 'date nil 'remote))
`----
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| I am Dyslexic of Borg. |
| Fusistance is retile. Your arse will be laminated. |
|------------------------------------<steve@sxemacs.org>---|
[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2006-01-31 1:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200601280127.k0S1RqD7007468@athyra.sfbay.sun.com>
[not found] ` <87irs44xm9.fsf@tleepslib.sk.tsukuba.ac.jp>
2006-01-29 20:05 ` [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers Reiner Steib
2006-01-29 22:24 ` Steve Youngs
2006-01-29 22:40 ` Reiner Steib
2006-01-30 1:16 ` Stephen J. Turnbull
2006-02-17 22:13 ` Date of XEmacs' Gnus (5.10.7) package (was: [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers) Reiner Steib
2006-01-30 23:24 ` [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers Mike Kupfer
2006-01-30 23:39 ` where does package-get-info get its info from? (was: gnus 5.10.7 not rendering Latin-1 headers) Mike Kupfer
2006-01-31 1:11 ` Steve Youngs [this message]
2006-02-18 0:34 ` [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers Mike Kupfer
2006-02-18 14:55 ` Stephen J. Turnbull
2006-02-19 12:48 ` Reiner Steib
2006-02-19 22:11 ` Mike Kupfer
2006-02-19 23:22 ` Reiner Steib
2006-02-20 7:41 ` Katsumi Yamaoka
2006-02-20 9:40 ` Katsumi Yamaoka
2006-02-20 11:30 ` Katsumi Yamaoka
2006-02-20 19:20 ` Mike Kupfer
2006-02-21 18:29 ` Mike Kupfer
2006-02-20 8:46 ` Stephen J. Turnbull
2006-02-20 9:41 ` Reiner Steib
2006-02-20 15:52 ` Stephen J. Turnbull
2006-02-20 21:26 ` Miles Bader
2006-04-09 8:14 ` Aidan Kehoe
2006-04-11 18:35 ` Reiner Steib
2006-04-13 22:34 ` Mike Kupfer
2006-04-14 8:14 ` Stephen J. Turnbull
[not found] <17990.13620.262943.353149@parhasard.net>
2007-05-13 9:20 ` Gnus: Autoloads for parse-time.el variables (was: [PATCH] package building problems.) Reiner Steib
2007-05-13 12:45 ` Aidan Kehoe
2007-05-14 17:21 ` Mike Kupfer
[not found] <m33awph096.fsf@Overgaard.mail.dk>
[not found] ` <878x6g6yz7.fsf@uwakimon.sk.tsukuba.ac.jp>
2007-10-06 16:09 ` [Bug: 21.5-b28] XEmacs/gnus refuses to open newsgroup with identical messages Reiner Steib
2007-10-07 13:47 ` Thomas Overgaard
2007-10-09 21:13 ` gnus 5.10.8 for XEmacs (was [Bug: 21.5-b28] XEmacs/gnus refuses to open newsgroup with identical messages) Mike Kupfer
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=microsoft-free.87u0bl42xa.fsf@youngs.au.com \
--to=steve@sxemacs.org \
--cc=ding@gnus.org \
/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 NNTP newsgroup(s).