Re: Committers: take care not to trash etc/package-index.LATEST.gpg

|--==> "SJT" == Stephen J Turnbull <stephen(a)xemacs.org&gt; writes: SJT> ... until somebody gets around to fixing the bug where this file is SJT> found by the package utilities. Tada... SJT> If you are running recent 21.5 in place, pui can and will assume the SJT> package-index in the source distribution is the index you want to use, SJT> and happily overwrite it. Not so, Gumshoe, but seeing as though it is now fixed this is now a moot point. :-) SJT> A simple solution seems to be just changing the name of that file to SJT> package-index.BOOTSTRAP.gpg A better solution would be to 'cvs up'. Here's the skinny on what happens now, Folks: There's a new user customisable variable, 'package-get-package-index-file-location' which defaults to either 'EMACSPACKAGEPATH' or 'user-init-directory'. This will mean that it is now possible to put your package-index file wherever you like. Behind the scenes when PUI is looking for your package-index file it checks (expand-file-name package-index-base-filename package-get-package-index-file-location). If it isn't writable, ask if 'user-init-directory' can be used. If it doesn't exist, ask if one can be created using the package-index from core as a template. At the end of the day, the only way to get PUI to write to 'core/etc/package-index.LATEST.gpg' is to set 'package-get-package-index-file-location' to do so. In the normal course of events PUI should _*NEVER*_ overwrite the core index file. A related note, the index file that is currently in core is giving a "The message is corrupt" error. The one that is currently in Pre-Releases on ftp.xemacs.org doesn't. If you get this error, just: M-: (setq package-get-require-signed-base-updates nil) -- |---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---| | XEmacs - The only _______ you'll ever need. | | Fill in the blank, yes, it's THAT good! | |------------------------------------&lt;youngs(a)xemacs.org&gt;---|